Sprint planning



Sprint planning

Attendees
Required: 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. (Kanban teams also plan, of course, but they are not 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.

Comments

Popular posts from this blog

Agile Bug Triage Meeting

Release Planning in Agile

Scrum Framework ( Scrum Methods)