Article

Scrum Sprint Planning


Scrum Sprint planning starts the sprint by choosing work for the sprint. The Scrum team participates to figure out, estimate and plan what needs to be done in the sprint. Time-box is 8 hours, for one month Sprint. The outcome is a Sprint Backlog which is composed of The Sprint Goal, the Product Backlog items selected for the Sprint, and the plan for delivering them.


Scrum team members and Sprint Planning

  • Product Owner should ensure that the most important Backlog items are known enough for a discussion to start.
  • Developers need to be aware of what is likely to go into the sprint and have thought about how the individual items could be implemented.
  • The Scrum master should be ready to help with the way Sprint planning is managed or to facilitate it if requested.
  • People outside the Scrum team can also participate if the Scrum Team needs their advice.


3 Sprint planning topics

  • Why is this Sprint valuable?
    • The product owner presents what should be done in a sprint to bring the greatest value. Based on that the Scrum team must create a Sprint goal during planning.
  • What can be done this sprint?
    • Items from the Product Backlog are selected. It must correspond to the Scrum team capacity which is based on the performance of the previous sprints.
  • How will the chosen work get done?
    • How to implement the individual items that were selected for the Sprint. Large items can be split for easier implementation. This is developers the responsibility.


Scrum Sprint Planning.

Similar posters

Maker's vs Manager's schedule
Maker's vs Manager's schedule The differences between a maker’s and a manager’s schedules stem from their respective workflows’ distinct nature. Makers rely on uninterrupted time blocks to tackle complex, creative problems requiring deep focus and sustained attention. Managers need flexibility to oversee multiple responsibilities, make decisions, and collaborate effectively across teams. As such, it is essential to thoughtfully assess...
Mission Statement
Mission Statement Long-term organization purpose, values and objectives. It should describe why it matters. This way it contributes to identity creation.
Value Stream Mapping
Value Stream Mapping The Value Stream Mapping is a Lean technique for managing flow and improving processes allowing to track the flow through a process.
Minto Pyramid
Minto Pyramid The Minto Pyramid Principle, a communication framework, advocates for a top-down approach to convey messages effectively
Spotify Health Check
Spotify Health Check The Spotify Health Check is a workshop, where teams assess their project and collaboration using 11 dimensions.
Maslow's Hierarchy Of Needs
Maslow's Hierarchy Of Needs Maslow's hierarchy of needs links basic human needs and desires, emphasizing that survival needs must be met before higher needs.
RACI Matrix
RACI Matrix RACI Matrix/Chart is the type of responsibility assignment matrix for effective work organization, communicating the responsibilities.
CEDAR Feedback
CEDAR Feedback CEDAR is a structured feedback model providing coaching opportunities via repeated revisiting and readjusting of the feedback and the goals.
STATIK Kanban
STATIK Kanban The Systems Thinking Approach To Introducing Kanban (STATIK) is a repeatable way to start with Kanban resulting in continuous improvement.
Data Model Canvas
Data Model Canvas The Data Product Canvas is a framework for developing data products based organized into 10 blocks within 3 domain areas.