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

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 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.
Kanban Practices
Kanban Practices Visualize Visualizing your work provides transparency, identifying the bottlenecks. Create cards for the items you work on. Think of the workflow – statuses that work items go through to make implicit policies explicit, which enable learning how the work works. Limit Work In Process Stop starting, start finishing. Limit the number of items being worked...
Theory Of Constraints
Theory Of Constraints The Theory of constraints says the throughput of any system is limited by at least one constraint slowing it down.
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.