Perhaps the most important practice for self-organization within the Scrum process is the Retrospective. Each sprint the team takes some time to assess their way of working and agree on improvement suggestions to work on and experiment with in the next sprint. When starting with an iterative and Agile way of working, the first Sprints are probably needed to get the most obvious impediments eliminated and to fulfill the basic prerequisites for iterative and Agile development (as described in the Nokia Test). Keep in mind however that circumstances will keep changing, so make adapting and improving part of your primary process.
Principles and values help to inspire improvement and pinpoint possible improvement areas. In the previous sections we talked about the Agile Manifesto and the Manifesto for Software Craftsmanship as value systems that can be used for this purpose. We talked about six XP practices for maintaining stability on a daily basis and XP’s Bill of Rights. We also introduced the Nokia Test as a set of prerequisites for a team to be Agile. RUP has 6 key principles that group twenty-five patterns for Business-Driven Development, OpenUP has four core principles grouping twenty-four practices.
To help teams in their improvement effort we have devised a concise set of principles that are inspired by all of the above guidance. They can be used to inspire discussion in a Retrospective and guide decision-making during a Sprint. Just write them on a flip over sheet, hang it in the team room and bring it to each Retrospective.
One of the things you can do with it is have people vote for the principles. Have every team member divide 3 marks, reflecting his personal sense of value of these principles and dicess the result.
Another way to get team involved in the improvement process is to create a mind map with the team starting with the above principles. You can use a whiteboard with colored markers or a collaboration tool that creates mind maps. Start with the above principles in the center as shown in Figure 28 and add detail and practices the team finds helpful further outward. You could also devote a separate mind map to each principle.
Principles and values help to inspire improvement and pinpoint possible improvement areas. In the previous sections we talked about the Agile Manifesto and the Manifesto for Software Craftsmanship as value systems that can be used for this purpose. We talked about six XP practices for maintaining stability on a daily basis and XP’s Bill of Rights. We also introduced the Nokia Test as a set of prerequisites for a team to be Agile. RUP has 6 key principles that group twenty-five patterns for Business-Driven Development, OpenUP has four core principles grouping twenty-four practices.
To help teams in their improvement effort we have devised a concise set of principles that are inspired by all of the above guidance. They can be used to inspire discussion in a Retrospective and guide decision-making during a Sprint. Just write them on a flip over sheet, hang it in the team room and bring it to each Retrospective.
 |
| Figure 27: Unified Principles for Iterative and Agile IT Development |
One of the things you can do with it is have people vote for the principles. Have every team member divide 3 marks, reflecting his personal sense of value of these principles and dicess the result.
 |
| Figure 28: Mind Map of Unified Principles |
loving the post. thanks.
ReplyDeleteHappy Independence Day Hindi