Sprint Planning

Purpose:

Refocus attention, minimize surprises, and (hopefully) guarantee better code is developed.

Objective:

Aligns the development team with the product owner.

Description:

This is where the work that will form the Sprint Backlog is selected and planned. The meeting is a collaborative one using the expertise of all parties. Indeed, the Development Team may invite others to attend to provide necessary domain expert technical advice.

In the first part of the meeting, the team decides what will be delivered. They consider the last increment and take into account their past performance and thus agree a likely capacity for what they can achieve this Sprint. From this they craft the Sprint Goal.

The second part of the meeting is devoted to how the work will be done. This is not a technical description of patterns of code, but rather a system of work and process. The planning becomes detailed here, separating the initial pieces of work into units of one day or less.

RASIC:

Inputs:

• Groomed Product Backlog

Outputs:

• Sprint Backlog Created
• Sprint Goal

Controls:

• <?>

Task Instructions:

Analyze Product Backlog

1. 1. Using Groomed Product Backlog, [the Scrum Master] with support firm the Product Owner and Scrum Team is responsible for analyzing the Product Backlog stakeholder needs, expectations,
      constraints, and external interfaces to organize into related subjects and remove conflicts.

Propose Sprint Goal

1. 1. Using <?>, [the Project Manager] is responsible for …..

Decompose User Stories into task

1. 1. Using <?>, [the Project Manager] is responsible for ….

Clarify the Acceptance Criteria

1. 1. Using <?>, [the Project Manager] is responsible for ….

Scrum Team agrees on capacity

1. 1. Using <?>, [the Project Manager] is responsible for ….

Scrum Team commits to Sprint Goal

1. 1. Using <?>, [the Project Manager] is responsible for …