Agile Definition of Ready & Done

Concept & Guidelines

Speaker’s Name, SAP
Month 00, 2017

PUBLIC

Partner logo
Objective

This guideline explains the Agile concept of:

 Definition of Ready
 Definition of Done
 Provides a proposal for Global IT Scrum projects

– Note: please finetune the definitions to your project specific situation

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Agile Concept Overview

Prepare Explore Realize

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:

Note: Definition of “ready” prevents sprint thrashing

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.

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

Example: Definition of Ready

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

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

The Definition of “Done”
Ensures a Real Working Product

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

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

Definition of “Done”

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.

Definition of Done for Sprint Definition of Done for Release

 Solution built and configured in  User Acceptance tested
DEV  Integration tested
 Solution is unit tested in DEV  User documentation completed
 Functionality tested by Process  Training material completed
Owner and Testers  No technical debt – e.g. no
 Functionality documented unfinished work or compromises (“we
 Bugs Fixed will get to this later”)
 Sprint Demo Completed  Functionality ready for release to
 Training material completed business
 Functionality transported to QAS
and ready for acceptance test

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

Example Definition of “Done”

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

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

A Product Backlog Has Flow Regions

In Sprint

Ready

Preparing

New

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9

How to Get User Stories Ready?
Two Options

1. Backlog Refinement Sessions (Grooming)

 Product Backlog items for coming sprints are reviewed and revised by
product owner and team (e.g. twice per week)
 Adding detail and estimates to the coming items of the product backlog
 Usually consumes no more than 10% of the capacity of the team
Ready User

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