What Does it Take to Become an Agile Developer?

What does it take to become an Agile developer? I recently was in a situation where the development team was completing tasks required for a sprint, but the overall stories were not being completed. The team allocated development tasks to individual developers and also allocated overall responsibility for each story to individual developers. However, for several sprints, the development tasks were completed but a number of the stories were not.

I don’t think the developers on the team clearly understood what it meant to be responsible for a story. I think most saw their primary responsibility as completing development tasks. Completing stories was seen as kind of an administrative coordination function. It’s more than that, in my opinion – a developer who takes responsibility for stories in a sprint needs to be responsible for:

  • Understanding the business purpose of the story and defining and analyzing possible alternative ways of satisfying the business purpose of the story
  • Planning and estimating development tasks with other developers that are required to fulfill the story
  • Working directly with the Product Owner to clarify and further define the details of how the story should be implemented
  • Providing guidance to other developers as necessary who are engaged in development tasks associated with the story
  • Taking overall responsibility for “shepherding” the story through the process all the way to (and including) UAT. The developer responsible for the story should lead the presentation of the completed story to the Product Owner in UAT (or Sprint Review)

I think it’s sometimes taken for granted that any developer can easily move into an Agile project – I don’t believe it’s that simple and my experience is that some developers have a hard time making that transition. Some developers just want to write code and are not even interested in taking on these additional responsibilities.

One thought on “What Does it Take to Become an Agile Developer?”

  1. Agreed. Success of any task/story is dependent on an individual’s involvement. It is critical that all assigned tasks within a story be coordinated amongst the responsible Developers. Each Developer knows how their contribution is intended to ‘fit’ in the puzzle and to move on to the next task/story without remaining ‘available’ impacts the team effort. This can place the burden of understanding a completed task on a less-skilled Developer that is trying to coordinate their work if/when issues arise.

Leave a Reply

Your email address will not be published. Required fields are marked *