A while ago, I published a post titled: Simple Cheat Sheet to Sprint Planning Meeting. Though I understand every team is different, I thought it would be helpful to those who are new to agile processes. People are always looking for cheat sheets, templates, and stuff like that. What is the harm of giving them what they want?
In retrospect, I think the harm is the lack of context. When people come to a training class, they are provided an ideal situation. Even the Scrum Guide was written as though you’ve been doing Scrum for a while. It doesn’t talk about things that happen leading up to your team’s first Sprint. It doesn’t talk about the complexity of scaling to the enterprise. It’s just vanilla.
I just got back from coaching a new team and I’ll be heading back next week to see how they are doing. To get them moving forward, I facilitated release planning and sprint planning. That’s where things can get interesting. What if your team has never done release planning or sprint planning?
The purpose of Release Planning is so the organization can have a roadmap that helps them reach their goals. Because a lot of what we know emerges over time, most of what we actually know is that we have a lot of unknowns and “unknown” unknowns in our future. Still, our organizations expect us to predict the future so they can make better decisions.
The purpose of the Sprint Planning is for the entire team to agree to complete a set of ready top-ordered product backlog items. This agreement will define the sprint backlog and is based on the team’s velocity or capacity and the length of the sprint timebox.
If your team is new to Scrum, you don’t have a velocity (rate of delivery in previous sprints) and you are not sure of your capacity (how much work your team can handle at a sustainable pace). What do you do?
The product backlog can address just about anything, to include new functionality, bugs, and risks. For the purpose of sprint planning, product backlog items must be small enough to be completed (developed, tested, documented) during the sprint and can be verified that they were implemented to the satisfaction of the Product Owner.
Again, your team is new to Scrum. How do they know what small enough is?
Product backlog items determined to be too large to be completed in a sprint, based on historical data of the team, should not be considered as sprint backlog candidates during the sprint planning meeting and should be split into smaller pieces. Remember, each story must be able to stand on its own (a vertical slice). It should not be incomplete or process based (a horizontal slice).
Again, your team is new to Scrum. They have no historical data.
The velocity of a team is derived by summing the estimates of all completed and accepted work from the previous sprint. By tracking team velocity over time, teams focus less on utilization and more on throughput.
If you have a new team, not only do you not have a velocity, you won’t have any completed work to compare your estimates to and you won’t know how many deliverables to commit to. What do you do?
You and your team need to just go for it! You keep track of what you are completing and collect historical data. You get through the sprint and establish some context for future sprints.
The first few sprints are going to be pretty rocky, until the team begins to stabilize. Just ask yourself. WWDD? What would Deming Do? Plan a little; Do a little; Check what you did versus what you planned; Act on what you discover. One challenge I’ve experienced is an organization wanting the team to make delivery commitments during their first few sprints. All of the upfront planning in the world is not going solve that problem. Once the team starts to deliver and their velocity improves, things settle down. But I’m asking the organization to give up the false predictability until things stabilize. That part is hard but critical.Follow @kelly_waters