This series of articles describes real life scenarios faced by Scrum Teams and some practical ways that have helped these teams ground.
Scrum is simple to understand but difficult to master. It is purposefully incomplete. The Scrum Guide says ” Scrum is built upon by the collective intelligence of the people using it. Rather than provide people with detailed instructions, the rules of Scrum guide their relationships and interactions.” This makes it challenging for Scrum Teams and Organizations to adapt their behavior while transitioning to Scrum Way of working. This series documents some such common scenarios and some possible way of actions that have helped Scrum Teams to deliver the best value that they can.
Some of the scenarios will be around Scrum Events, How the Scrum Teams work in Self-Managed Cross Functional ways and also around some of the regular Product Development activities like sizing, ordering and Product Backlog Management
- Sprint Planning – Sprint Planning is the first event of the Sprint. Its also longest of the four formal Scrum Events contained within the Sprint. When done well Sprint Planning makes it easy for the Scrum Team to deliver Value during the Sprint. However, this Scrum Event often poses challenges for the Scrum Team.
- Daily Scrum – Daily Scrum is a by and for Developers Scrum Event that helps Developers to create a plan for next day. This is often a misunderstood Scrum Event as an opportunity take a status – Few of the commonly faced scenarios are documented here.
- Sprint Review – Sprint Review is the only Scrum Event where stakeholders are the key participants. This is a very forward looking event where Scrum Team and Stakeholders decide together on the future adaptations for the Product!
- Sprint Retrospective – Often people find it challenging to keep Sprint Retrospective positive. Look at some real life scenarios Scrum Teams face during Sprint Retrospective.
- Product Backlog Refinement
- Challenges Faced when multiple Teams are working on the Same Product
- Challenges Faced by distributed Teams.
- Scenarios Around Role Sharing – where the same person is rendering multiple accountabilities.
- Scenarios around sizing /velocity
- How Scrum Master Serves The Scrum Team
- How Scrum Master Serves The Organization