The current version of The Scrum Guide is getting updated. Here are the things I wish the new updates could address (a) Daily Scrum (b)Development Team (c) Product Owner (d) Sprint Backlog and incomplete PBIs at the end of the Sprint (e) Acceptance of Work by Product Owner (f) Increment (g) What is the Product
Scrum, today, has become the most popular framework. Naturally, the folklore around it also has grown over the course of time. Scrum was first published in 1995, and Scrum Alliance officially founded in 2001. During those times, the main source of Scrum was the creators of the framework. Naturally, word of mouth has its limitations… Continue reading Scrum: folktales, facts, alternate- facts, and other nonsense !!
Every Sprint, the Development Team is responsible for building a "releasable" Product Increment. The Product Owner may choose to release it or may not choose to release the Increment at the end of the Sprint. Scrum does not prescribe a release frequency (i.e. PBIs can be released multiple, times a day, once a Sprint, once… Continue reading This is how you hit the ball out of the park in your first Sprint
Some time back, I was in a Sprint Planning meeting with my team. Listening to the conversations, it was clear that the team had a pretty good idea on what to do and how to do, but, I sensed that there quite a bit of ambiguity and uncertainty about how the planned items might… Continue reading Scrum Master Tips: One Practice to Identify and Reduce Risks During Sprint Planning
When organizations are adopting Scrum, they are always confronted with how long their Sprints should be. Scrum merely provides guidelines that Sprints can be anywhere from 1 week to 4 weeks long. The Sprint is a feedback loop, providing an opportunity for the stakeholders and the Scrum Team to Inspect and Adapt (the product, and the way… Continue reading How Long Should my Sprints be?