The document discusses the definition of ready as it relates to user stories and sprints in agile software development. It provides details on what constitutes a user story being ready, including it being defined, having acceptance criteria, identified dependencies, sized by the team, and more. It also lists criteria for a sprint to be ready, such as the sprint backlog being prioritized and containing all committed work with no hidden work, and all team members having calculated their capacity for the sprint.

1. Defini&on
of
Ready

2. Do something cool
As a
User
I want to
do something cool with the product
So that I can
benefit in some way
Concept
Happy
User
ken.power@gmail.com
@ken_power

3. Level
of
Focus
on
the
User
Story
Product
Owner
Team
Concept
Time
ken.power@gmail.com
SStart
Done
Accept
SEnd
Ship
It
@ken_power

4. Level
of
Focus
on
the
User
Story
Done
Product
Owner
Team
Concept
Time
ken.power@gmail.com
SStart
Done
Accept
SEnd
Ship
It
@ken_power

5. Level
of
Focus
on
the
User
Story
Done
Ready
Product
Owner
Team
Concept
Time
ken.power@gmail.com
SStart
Done
Accept
SEnd
Ship
It
@ken_power

6. Level
of
Focus
on
the
User
Story
Done
Ready
Product
Owner
Team
Concept
Time
ken.power@gmail.com
SStart
Done
Accept
SEnd
Ship
It
@ken_power

7. Level
of
Focus
on
the
User
Story
Done
Ready
Product
Owner
Team
Concept
Time
ken.power@gmail.com
SStart
Done
Accept
SEnd
Ship
It
@ken_power

8. Level
of
Focus
on
the
User
Story
Done
Ready
Product
Owner
Team
Concept
Time
ken.power@gmail.com
SStart
Done
Accept
SEnd
Ship
It
@ken_power

9. Level
of
Focus
on
the
User
Story
Done
Ready
Product
Owner
Team
Concept
Time
ken.power@gmail.com
SStart
Done
Accept
SEnd
Ship
It
@ken_power

10. Level
of
Focus
on
the
User
Story
Done
Ready
Product
Owner
Team
Concept
Time
ken.power@gmail.com
SStart
Done
Accept
SEnd
Ship
It
@ken_power

11. Level
of
Focus
on
the
User
Story
Done
Ready
Product
Owner
Team
Concept
Time
ken.power@gmail.com
SStart
Done
Accept
SEnd
Ship
It
@ken_power

12. Why
have
a
Defini&on
of
Ready?
• So
everyone
knows
when
a
User
Story
is
really
ready
to
be
taken
into
a
Sprint
– It
does
not
need
to
be
“100%
defined”
with
all
acceptance
criteria,
etc.
– It
does
need
to
be
“ready
enough”
so
that
the
team
is
confident
they
can
successfully
deliver
ken.power@gmail.com
@ken_power

13. Defini&on
of
Ready
for
a
User
Story
• User
Story
defined
• User
Story
Acceptance
Criteria
defined
• User
Story
dependencies
iden&fied
• User
Story
sized
by
Delivery
Team
• Scrum
Team
accepts
UE
artefacts
• Performance
criteria
iden&fied,
where
appropriate
• Person
who
will
accept
the
User
Story
is
iden&fied
• Team
has
a
good
idea
what
it
will
mean
to
Demo
the
User
Story
ken.power@gmail.com
@ken_power

14. Defini&on
of
Ready
for
a
Sprint
• The
Sprint
Backlog
is
priori&zed
• The
Spring
Backlog
contains
all
defects,
User
Stories
and
other
work
that
the
team
is
commiUng
to
– No
hidden
work
– Examples
of
‘other
work’
might
include
lab
setup,
build
environment
maintenance,
crea&ng
a
test
app
• All
team
members
have
calculated
their
capacity
for
the
Sprint
– Full&me
on
project
=
X
hours
per
day
• All
User
Stories
meet
Defini&on
of
Ready
ken.power@gmail.com
@ken_power