Agile Iteration Planning

The whole team attends the IPM (Iteration Planning Meeting). The entire team includes the stakeholders, the programmers, the testers, and the project manager. The goal of each iteration is to produce data by getting stories done. The stakeholders will have read the estimated stories and sorted them in the order of business value.

An iteration should contain about the same number of stories as there are developers on the team. The team should focus on stories rather than tasks within stories. Stories are chosen by and belong to individual programmers. Managers and leads will be tempted to assign stories to programmers. This should be avoided. Let the programmers negotiate amongst themselves to promote collaboration is far better. After all, agile teams should be self-organizing teams.

When a team practices Collective Ownership, knowledge becomes distributed across the team. Each team member gains a better understanding of the boundaries between modules. And of the overall way that the system works.

—

[¹]: Robert C. Martin (2019): (Clean Agile: Back to Basics (Robert C. Martin Series))