Presentation on Requirements Discovery for BADD

1. Requirements
Discovery
David
Hawks
@aus7nagile

2. What’s
your
BIGGEST
BEEF
with
User
Stories?
Get
together
with
a
partner
and
share
stories
about
Stories.
Write
down
your
partner’s
biggest
beefs.

3. Sharing
Time!
• How
about
some
volunteers
to
share
what
you
heard
from
your
partner?
• Share
the
beef!

4. Let’s
Remodel!

5. Instruc7ons
• Work
at
your
table/with
a
small
group
of
4
–
5.
• Some
of
you
volunteer
to
be
the
“contractor”
(the
development
team
or
project
manager)
• The
remaining
members
are
the
customer
• The
customer
picks
some
kind
of
home
remodeling
project
• Examples:
– Remodel
bathroom
– Remodel
kitchen
– Add
a
story
to
the
home

6. Write
the
Name
of
the
project
on
a
card
and
the
contractors
should
interview
the
customers
to
understand
the
job.

7. Document
the
condi7ons
of
sa7sfac7on
for
your
story

8. The
Three
C’s
Card

9. The
Three
C’s
Card
Conversa7on

10. The
Three
C’s
Card
Conversa7on
Confirma7on

11. User
Stories
As a <WHO>
I want <WHAT>
So that <WHY>

12. User
Story
Example
As a frequent flyer
I want to rebook a past trip
So that I save time booking
trips I take.

13. Acceptance
Criteria

14. Independent
Nego7able
Valuable
Es7mable
Small
(a.k.a.
Sized
Appropriately)
Testable

15. +
+
Backlog
Grooming
(Regular
cadence
weekly
or
bi-­‐weekly)
This
is
where
the
conversa7ons
happen

19. But
Dave,
Everything
doesn’t
fit
in
a
Sprint!

20. Detailed Appropriately
21
100
40
100
100
20
20
13
13
8
20
8
13
5
3
5
3
5
3
Product
Backlog
Epics
Large
Lower Priority
Future Release
Backlog
Items
(What is Requested)
Estimated in Points
Small – Sprint Sized
Detailed
Higher Priority
2-3 Sprints Worth
Sprint
Backlog
Tasks
(How to Get it Done)
Estimated in Hours
Tasks Required to Complete Backlog
Items
Sized Less than a Day
Individual Workable Items
Release

21. Emergent

22. Richard
Lawrence’s
Story
Splieng
Strategies
• Workflow
Steps
• Business
Rule
Varia7ons
• Major
Effort
• Simple
/
Complex
• Varia7ons
in
Data
• Data
Entry
Methods
• Defer
Performance
• Opera7ons
(e.g.
CRUD)
• Break
out
a
Spike

23. Execution
• Agile
• Scrum
• Predictability
• Velocity
• Test
Automation
• Continuous
Integration

24. 64% of the features
we build in the
software industry are
Rarely or Never Used!

25. ExecutionDiscovery

26. Discovery
• Lean
Startup
• User Story
Mapping
• Design
Thinking
• Lean UX

27. Build
Feedback?
Idea
Product

28. Build
Feedback?
Idea
Product
How do you
know you are
building the
right thing?

29. Build
Feedback?
Idea
Product
When do you
find out if you
are right?

30. How long is the
Release cycle?
(From Concept to
Customer)
How many
features are
released together?
How is success
determined?
Your
Product
Today

32. How long is the
Release cycle?
(From Concept to
Customer)
How many
features are
released together?
How is success
determined?
Your
Product
Today
In the
Video
What
was the
impact?

33. Build
Idea
Product
Measure
Learn
Data

34. Build
Idea
Product
Measure
Learn
Data
The Goal is to
Shorten the
Learning Cycle

35. Turn your Requirement
into an Hypothesis
If we do X then Y% of customers will
behave in way Z

36. Paper Prototyping

37. Explainer Video

38. Facade

39. Identify the riskiest
assumption for your
current product.
How could you
validate (or invalidate)
it quicker?

40. David
Hawks
David@AgileVelocity.com
www.AgileVelocity.com
Blog:
www.Aus7nAgile.com
Twijer:
@Aus7nAgile
Thanks!