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

Classes of Service (CoS)
Classes of Service (CoS) Classes of service (CoS) provide a transparent way of categorizing the incoming work items and ensuring they are properly prioritized and governed to lead to meeting customer expectations. They enable managing risk, priorities, and cost of delay. Expedite High-priority items that should be worked on as soon as possible. Expedite class work items have critical...
Seven wastes of software development
Seven wastes of software development Similar to what TPS identified as seven categories of waste in manufacturing, also software development has its own wastes.
Core Kanban Practices
Core Kanban Practices One of the few rules or practices which are the foundation of Kanban are its 3 core practices: Visualize, Limit WIP, and Manage flow.
The prime directive of agile software development
The prime directive of agile software development Acronymat poster: The prime directive of agile software development - Never be blocked, the system must work all the time.
AIDAOR
AIDAOR The AIDAOR is a hierarchical model, where a persona moves through a series of cognitive steps before and after making a purchase decision.
Little's law
Little's law Little’s Law is a theorem for queuing systems. It determines the average number of items in a stationary queuing system
User Story Creation
User Story Creation Creating a User Story is a continuous process based on the 3Cs phases, supported by INVEST, 5Ws, and the Definition of Done.
Radical Candor
Radical Candor Radical Candor is a framework describing four different behaviors. In order to become Radically Candid you need to understand all four types.
GSD / Get Stuff Done Whee
GSD / Get Stuff Done Whee Get Stuff Done Wheel is a framework for aligning and guiding the work of a team. It allows teams to deliver remarkable results more quickly
AIDA Model
AIDA Model The AIDA model is a model, where a persona moves through a series of steps to make a purchase decision, used in marketing, sales, planning...