Sprint Planning

Attendees: Whole Scrum Team (including dev team, scrum master and product owner)

Duration: Ideally 1 hour per sprint week. Example – 3 hrs for a 3 week sprint and 4 hrs for a 4 week sprint

When: Before a Sprint begins.

Why: To populate the sprint backlog for the coming up sprint.


  1. Access team availability to gauge how many stories can be completed in a sprint
  2. Define Sprint Goal
  3. Product owner pull stories from prioritized product backlog
  4. Team discuss the user stories
  5. Team throw estimates on the stories in story points
  6. Discussed and estimated User stories are pulled into sprint backlog
  7. Team commits to the sprint goal and the user stories in the sprint backlog.

Helpful Tip(s): Refinement meetings ( or grooming meetings) before the sprint planning meeting help in hashing out intricate details of the planned stories for the upcoming sprints.


Like my blog? 


Sprint Review or Demo

Attendees: Whole Scrum team (including dev team, ScrumMaster and Product owner)

Duration: 30 – 60 minutes

When: Last day of a sprint after all stories are ‘Done’

Why: Sprint Review is more of a celebration of achievements made in a sprint. It is the time to showcase the milestones achieved in a sprint to the stakeholders.


  1. Scrum Master facilitates a meeting with the stakeholders either in the team area or in a conference room
  2. Scrum Team displays the working features they developed in the sprint.
  3. Stakeholders provide feedback

Helpful Tip(s): A lot of teams like to demo their sprint achievements on the next day after the last day of the sprint as all the stories are complete and code is merged by then.


Like my blog?