Scribd
Upload
5 views

Sprint Planning Backlog Goal

Uploaded by

maldup
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
5 views

Sprint Planning Backlog Goal

Uploaded by

maldup
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 19

Sprint Planning

Sprint Backlog
Planning Process
The Purpose of Sprint
Planning

Establish goals for your sprint

Choose the user stories that support those goals

Create a sprintEstablish
backlog goals for your
sprint
Sprint Planning

*duncanhalley
Sprint Planning
The Sprint Planning meeting should be more lightweight as the explanation of the
stories is done in product backlog refinement.

Sprint planning is needed to feed the sprint with stories that are ready (DOR).
At the same time the PO needs to take the technical advice of the team into account!
Dependencies, testing issues, etc... are part of the deal.

The priority of what comes into the sprint is communicated by the PO.

These stories will be


1. put into the sprint
2. estimated in the planning meeting (only and only if last minute stories were added
since the PBR that have received top priority!)
3. committed

Contd…
Sprint Planning
Why?

Knowing how much the team can deliver is of crucial importance for the rest of the
organisation: The PO, the customer, managing expectations, release activities,
budgetary reasons, ... it will all be based upon this.

The nice thing: it's up to the team to determine how much they can achieve in a
sprint.
This amount will grow according to flexibility, knowledge, learning, ...

The trend of the amount of work a team can absorb is the Velocity.
By tracking this we are building up the predictability of the team.

Goal?

Having a confirmation from the Team, what the Team believes they can deliver the
coming Sprint.

Contd…
Sprint Planning
What?

Sprint Planning Part 1: Fill up the sprint

Starting from a refined and estimated backlog, add items to the sprint.
During this process the priority of the chosen items is discussed with last-minute info if
needed. (e.g. dependencies, ...). Usually the PO has most of the information but input
from the team about for example dependencies that have come up is crucial.
When the team has the feeling it's about enough to digest for a sprint we validate this
with the PO and move to part 2 of the sprint planning.

If it appears the Team is not confident on the refinement questions, that story is NOT
taken into the sprint! Not even if a whole dependency flow is blocked by it.
This is a hard line of discipline to keep in mind: We do NOT start working on a story
that is not meeting the Definition Of Ready (DOR)

Contd…
Sprint Planning
Sprint Planning Part 2: Tasking out

What follows is tasking out the stories.

The story should be sliced up small enough ( sub-tasking) and understood well enough to
estimate and to get to done within one sprint.
For each story the question is asked what are all the steps that need to be done in order
to get this story completely finished as indicated in the team's Definition of Done

If the team feels while tasking out that they might have overestimated themselves, this is
the moment to say so and discuss with the PO which story can be left out. On the
contrary, if discussion during the tasking out indicates that the solution is much simpler
than anticipated, the PO can propose additional stories to be added and tasked out.

What the team finally believes they can do, is the formal confirmation which is
communicated to the PO

This is scope of the Sprint


Sprint Planning
Sprint Planning Part 2: Tasking out

SMART Tasks

S – Specific
The task is specific enough that everyone can understand what's involved and prevents
overlapping.
M – Measurable
The team can measure that the task is Done. This requires the team to have a clear
definition of Done.
A – Achievable
The task is achievable by whoever from the team takes on this work.
R – Relevant
Every task should be relevant by contributing directly to a story and each task can be
explained/justified.
T – Time-boxed
A task should be time-boxed by setting the right expectation for how long it should take
to complete the task.
Sprint Backlog
A sprint backlog is the result from the Sprint Planning Session and is a list of work items
the team is confident to be able to finish within the next iteration.

The sprint backlog is the artefact that allows the team to collaborate on a single work
item and support each other as well as evaluate their progress during the The Daily
Standup.

You might also like