Blog

Reach Us

Sprint Planning

17 Jul 2017

Sprint Planning

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.

 

Product Owner

Scrum Master

Development Team

Goal

Occurs at the beginning of the Sprint to collaborate and come up with work plan for the Sprint

Inputs

  • Product backlog
  • Latest product increment
  • Projected Development team’s capacity during the Sprint
  • Past performance of the development team
  • Definition of “Done”
  • Retrospective Improvements
  • Impediments

General Responsibilities

Ensure that PBI’s under discussion are “Ready” for selectionFacilitates the event

Ensure attendees understand the purpose

Maintain Time-box

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 teamDecide 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

Outputs

Sprint Goal:

  • Objective set for the Sprint based on the selected PBI’s
  • Guidance for Development Team for the Sprint
  • Gives some flexibility to Development Team regarding implementation of the selected functionalities
  • Should be a logical function that makes Development Team work together rather than working in silos
  • Sacrosanct and doesn’t change throughout the Sprint

 

Sprint Backlog:

  • It contains selected PBI’s, tasks breakdown and plan to deliver the product Increment
Do’s
  • Be prepared with PBI’s under discussion
  • Follow Scrum values throughout the meeting
  • Keep stakeholders abreast with the decision post the meeting
  • Listen actively
  • Liaise between Product Owner and Development Team
  • Help keep the discussions on track and time boxed
  • Follow Scrum values throughout the meeting
  • If necessary to keep discussion on track, coach the team on purpose of the meeting
  • Ensure appropriate understanding of PBI’s and acceptance criteria
  • Be cognizant of “Done” and Retrospective commitments
  • Follow Scrum values throughout the meeting
  • Ensure everyone is aware of impediments you foresee that are out of your control
Don’ts
  • Negotiate on “Done” for more PBI’s to be completed
  • Take sides during the discussion
  • Overcommit