Scrum Ceremonies – Sprint Planning Meeting
Attendees: Development team, scrum master, product owner
When: At the beginning of a sprint.
Duration: Usually an hour per week of iteration–e.g. a two-week sprint kicks off with a two-hour planning meeting.
Agile Framework: Scrum. (Other frameworks also plan, of course, but they are notnecessarily on a fixed iteration schedule with formal sprint planning)
Purpose: Sprint planning sets up the entire team for success throughout the sprint. Coming into the meeting, the product owner will have a prioritized product backlog. They discuss each item with the development team, and the group collectively estimates the effort involved. The development team will then make a sprint forecast outlining how much work the team can complete from the product backlog. That body of work then becomes the sprint backlog.
Sprint Planning Meeting
Inputs:
Team Velociy
Product Backlog
Technology
Business Conditions
Curent Situation
The Meeting:
Sprint Prioritisation
Prioritise and Analyse the Product Backlog
Set a Goal for the Sprint
Sprint Planning
Product Owner sets out the Sprint Goal
Team discusses what can be done in the Sprint
Everyone agrees what can be done
Team plans the Tasks that need to be completed
Output:Sprint Goal
Output: Sprint Plan
Expert Advice: Use the sprint planning meeting to flesh out intimate details of the work that needs to get done. Encourage team members to sketch out tasks for all stories, bugs, and tasks that come into the sprint. Foster discussions and gather consensus on the plan of action. Effective planning significantly increases the team’s chances of success meeting the commitments of the spri.