Beruflich Dokumente
Kultur Dokumente
PUBLIC
Partner logo
Objective
R
E Sprint backlog/
A Revised prioritizes
product backlog
D
Determine initial Prioritized product
high level scope backlog with user
Y Sprint Sprint
Retrospective Planning
and Plan stories in Ready
State
2-to-4 wks.
cycle
Sprint
Sprint Review Realization &
Daily Scrums
Work product Work product
Release increment D
O
N
Run Deploy
E
“Don't let anything that's not READY into your Sprint, and let nothing escape that's not DONE.”
(Serge Beaumont about definition of ready)
© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3
Definition of Ready
The team will only take work into a sprint when the following criteria are satisfied:
Negotiate
Definition of Ready
Why? Business value Team decides if OK
Ready
What? Outcome vision Describes the backlog before
How? Implementation sprint
strategy and cost
Enough for 1, 5-2 sprints? Quality checklist
Granularity OK?
Definition of Ready
The backlog items have been understood.
It is described for each backlog item individually.
Is (mostly) static over the time.
It is negotiated between the customer and Service & Support Team.
The team will only take work into a Sprint when the following criteria are satisfied:
The epic/story is on the Corporate Backlog
The Team understands the problem
The Team understands why this is important
This story has been estimated by the Team
The Team knows how to demo this story to the Product Owner
The Team has insight in the context of the story
Acceptance criteria for the Product Owner are clear and agreed upon
Acceptance criteria for operations are clear and agreed upon
Negotiate
Definition of Done
Acceptance tested Product Owner decides is OK
Done
Unite tested Describes the product at the end of the sprint
No increased technical debt
Documentation in order Quality checklist
Conform standard X Static constraints and requirements
Can vary over time
The team will only deliver products that satisfy the following criteria:
Define when you consider backlog item done. Definition must be clearly understood by all involved in the
project. See examples below for recommended definitions.
Ensure that the estimates in the backlog include all activities required for completion of sprint and for
completion of release.
The team will only deliver products that satisfy the following criteria:
The software has been developed
The software works technically correct
The software works functionally correct
The software has been documented appropriately
The software is deployed on the ‘X’ environment
The agreed acceptance criteria from operations (see DoR) are review ready
The team dashboard is up to date
In Sprint
Ready
Preparing
New
Ready
Story
New
2. “Ready” User Stories (Spikes)
Determine User Stories which need to be made “ready”
Incorporate those into the sprint planning meeting
Ready
Done
“Ready” and “Real” user stories are worked on in parallel
Tasks are defined to make user story “ready” (“Real”) User
Story
Rule of Thumb:
Have enough user stories ready for 2-3 sprints
© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10
Thank you.
Contact information:
F name L name
Title
Address
Phone number
Partner logo