Being the first event for Scrum team at the start of a Sprint, Sprint Planning tends to set the tone for the entire duration of Sprint. Doing the right things at this stage will help reduce the stress on the team and prevent cascading effect of any issues that may hamper the Sprint progress. With that in mind, I wanted to share a ready reckoner for Sprint Planning.
|Occurs at the beginning of the Sprint to collaborate and come up with work plan for the Sprint|
|Ensure that PBI’s under discussion are “Ready” for selection||Facilitates the event|
Ensure attendees understand the purpose
|Invite technical and/ or domain experts as needed|
Part I: What work can be done?
|Discuss the objectives and PBI’s (wish list) for Sprint|
Provide PBI’s details
|Select and forecast the functionality to be developed|
Craft Sprint Goal
Part II: How the work will get done?
|Clarify selected PBI’s and make trade-offs|
Discuss Acceptance criteria
|Be a neutral party to facilitate negotiations between PO and Development team||Decide how selected PBI’s will be converted to “Done” product increment|
Renegotiate selected PBI’s with Product Owner, if too much or little effort is needed to convert the PBI into product increment
Create Sprint Backlog: PBI’s and delivery plan