- Meeting for scrum team to retrospective on how the Sprint went with respect people, process and tools.
- Team identifies what went well and what can be improved.
- Team identifies a plan to implement identified improvements.
- Other stakeholders are not allowed.
- An opportunity for the team to make continuous improvements.
- Maximum time box of 3 hours for a 4 week Sprint
- The retrospective meeting is not conducted.
- Identified improvements are not followed up with actions.
- The scrum master or/and development team does not attend.
- Other stakeholders are not allowed.
- Maximum time box of 3 hours for a 4 week Sprint.
Each Sprint in Scrum has to a meeting – Sprint Retrospective at the end. It is very essential that the Scrum Master never allows the team to skip these meetings. These meetings uplift Inspect and Adapt principles of Scrum and help the product to be better and better after each Sprint.
Team along with Scrum Master asks 2 questions:
- What went well in last sprint?
- What could be improved in next sprints?
- Ensure that everyone can speak freely.
- Sprint retrospective meeting is not the place for advocating ones personal agenda.
- Do not play the blame game.
- Do not allow vague statements.
- Transform identified improvements to concrete action points.
- Process improvements are made at end of every Sprint - ensures that the project team is always improving the way it works.
- The Retrospective is a collaborative process between all members of the Team, the Product Owner, and the Scrum Master.
- All team members identify what went well and what can be improved
- Scrum Master prioritises actions and lessons learnt based on Team direction
- Team devises solution to most vexing problems - helps to build the team ownership and self management.
- Helps the team formation and bonding as any areas of conflict can be identified and dealt with.
No comments:
Post a Comment