NEXTUP MADNESS: SCORE 15% OFF KANBAN TRAINING
If anyone has ever been in a painful sprint planning meeting, one of the things that makes a sprint planning meeting is that the product backlog items (PBI)/user stories/requirements brought into sprint planning aren’t quite ready for the Scrum team to review. They are half written, sometimes without acceptance criteria, not ordered, and brought in […]
If anyone has ever been in a painful sprint planning meeting, one of the things that makes a sprint planning meeting is that the product backlog items (PBI)/user stories/requirements brought into sprint planning aren’t quite ready for the Scrum team to review. They are half written, sometimes without acceptance criteria, not ordered, and brought in without any dev team members having seen the items before sprint planning.
To help address this issue, there is a concept called “definition of ready.” It’s not an official Scrum concept, but there are quite a few advantages to having a definition of ready, but it should also be noted that some Agilists have argued against definition of ready. The main argument is that it promotes too much major upfront planning and leads to over-engineered requirements, which is a valid concern. To combat this, the definition of ready needs to be lightweight while ensuring the team has enough of an understanding of the needs to reach the next steps of implementation. The critical benefit of a definition of ready is a shared understanding of what it means for PBI to be ready for sprint planning and to be worked on.
One of the most well-known forms of definition of ready is INVEST from Bill Wake. INVEST stands for:
While there is a lot of value in Bill’s INVEST idea, below is an updated version that is more actionable:
First, after the Product Owner has created the PBI, have at least two dev team members (you can have as many as you like, but at least two) review the PBI. When they review the PBI, they should be able to address the following:
Note that this conversation should happen prior to sprint planning to ensure the PBI is ready. If all six points are well aligned, then you are ready for the PBI to be reviewed by the entire Scrum team. By doing this, we have a greater guarantee of an effective sprint planning meeting and greater probably of success in our sprint.
What is the difference between Scrum and Kanban?
Both Scrum and Kanban provide principles and practices that you can apply to deliver high-quality...
How Agile Leads to Cost Savings
In the past two decades, Agile methodologies like Scrum and Kanban have exploded in popularity...
Optimize the Whole: Lessons From a Past Tester
Sub-optimization happens when we apply an improvement measure or process to one component of a...