Developing Developers

You may have recently read about the Scrum Master’s To Do list. The last To Do list in our Perfect Development series we are going to write about is the Developer’s To Do list, which contains the following:

  • Focus on the creation of the Product Increment.
  • Cooperate with the Product Owner and Scrum Master on required User Story clarification and refinement when needed.
  • Select additional work from the Product Backlog when all planned work is finished (or is irreversibly impeded in the Sprint).
  • Self-organize with the rest of the team.

 

You may be familiar with some of these points, as we touched on these topics in previous articles, but let’s refresh our memory.

 

Focus on the creation of the Product Increment.

This topic has already been discussed in the previous article, but there is something to add. I would like to point out the importance of focus. When following the first mode of planning described here, you will find an important statement: “They (Developers) choose the right amount to take into the next Sprint and are committed to do their best to develop the working increment by the end of the Sprint.” To be successful, they need to focus on the creation of the Product Increment.

 

Cooperate with the Product Owner and Scrum Master on required User Story clarification and refinement when needed.

We have already written about this point in several articles. You can read more about refining here and here.

 

Select additional work from the Product Backlog when all planned work is finished (or is irreversibly impeded in the Sprint).

There are several reasons for Developers taking additional work from the Product Backlog. The Product Owner could set the upper limit for the Developers’ Sprint capacity (that is the second mode of planning), the Team could underestimate themselves, the work in progress could be blocked, but the team can’t unblock it during the Sprint, or the scheduled User Stories finish sooner than expected. Whatever the reason, it should be discussed during the Sprint Retrospective.

If Developers take more work from the Product Backlog, there are rules which need to be applied. You can read about them in the article Estimate and Select from the Top of the Product Backlog.

 

Self-organize with the rest of the team.

Self-organizing does include all members of the team; it is not about just organizing oneself. What we should strive for is to have the whole team self-organized. We want people to work together, be proactive and communicate the problems (but not only the problems, of course) no matter where we are in the Sprint or in which event.

 

And that was it. Next time we will write about the first few Perfect Development rules. See you soon!

You may also like:

Deviations from Optimal Planning – Hungry Hungry Developers

In the previous article, we spoke about Product Owners forcing capacity on the Developers, and now we are going to have a look at the…