Posts Tagged ‘Sprint planning’
Team Velocity and Story Points in Scrum
Learn more about Scrum and Team Velocity by reading a short piece from Dan Rawsthorne and Doug Shimp’s newly released second edition of “Exploring Scrum: The Fundamentals”
Read MoreTeams Perform with Agreement-Based Planning
Scrum teams perform best when they take the work. This is why Scrum uses a pull mechanism, facilitated by Agreement-Based Planning, instead of push when doing the work. In other words, work is pulled through the pipeline by people rather than pushed through the pipeline by process. To help teams pull work through, the mechanism…
Read MoreAgreement-Based Planning
Agreement based planning is an alternative method to capacity based planning and involves the team in defining it’s capacity through commitment to small pieces of work.
Read MoreWhen are you ready for sprint planning?
There are a number of things you should do before you can even begin planning. The most important thing you can do is make sure that your Product Owner is prepared,
Read MoreHow do you fill a sprint?
After a Story is committed to, the Team (with the PO in the lead) has the option to reprioritize the Story list, and the Team takes the next one to consider.
Read MoreShould the team be allowed to drop the retrospective?
Of things to watch out for and not allow this is high on my list. It boils down to this rule: If the team is not doing a retrospective then they are not doing scrum.
Read MoreWhen should a sprint end?
Without time-boxes we rapidly loose our sense of predictability and the amount of complexity we tackle in each bite drifts upward.
Read More