Easy Agile

Sprint Planning What is it? In textbook Scrum, the purpose of the Sprint Planning Meeting is for the entire team to agree to complete a set of ready top-ordered product backlog items. This agreement will define the sprint backlog and is based on the team’s velocity or capacity and the length of the sprint timebox. Who does it? Sprint planning is a collaborative effort involving: ScrumMaster – to facilitate the meeting Product Owner – to clarify the details of the product backlog items and their respective acceptance criteria Entire Agile Team –to define the work and effort necessary to meet their commitment to complete product backlog items Before You Begin Ensure all items to be discussed meet the teams definition of “ready”, to include (for example): relative story point value dependencies removed testable examples clearly defined acceptance criteria All items to be discussed reflect the greatest needs as identified by the Product Owner at th...

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.