Sprint planning is the topic for Scrum Dynamics episode 13. In this episode I cover all the aspects of sprint planning for Dynamics 365 projects:
What is sprint planning and when does it take place?
Who attends sprint planning, and what to do if the product owner can’t make it?
How long is sprint planning?
What happens during sprint planning? Sprint goals, sprint backlog forecasting, Dynamics 365 feature design.
What’s needed for sprint planning?
And and I share my top ten tips for successful Dynamics 365 sprint planning workshops:
Take a break at the end of part two of the sprint planning workshop.
The product owner should draft the sprint goal before sprint planning.
If your product owner can’t attend, run sprint planning as best you can and then run a confirmation session as possible as possible.
Consider carefully whether enumerating and estimating tasks will improve productivity or not.
Use the storytime session immediately before sprint planning to ensure all the high-value items meet your definition of ready.
Don’t fill your sprint backlog full of items to match your forecast capacity. Leave a buffer.
Don’t forecast the completion of a spike and its related story in the same sprint.
Play first of five to measure everyone’s level of comfort with the forecast sprint backlog.
The scrum master’s job is to help the team fine-tune its forecast sprint backlog.
Run sprint planning in the afternoon on a Tuesday, Wednesday or Thursday.