The document discusses the benefits of using LEAN and testable user stories, including expediting time to market, reducing miscommunications, allowing for faster understanding through visual depictions, and reducing meetings. It provides examples of typical user story layouts including acceptance criteria in a Given/When/Then format. Finally, it advocates keeping supporting documentation visual rather than textual.

1. LEAN, Testable Story Authoring
www.agilemethodology.us
Robert R. Betcher PMP, CSM & ACP July 01, 2015

2. 1
Why LEAN & Testable Stories?
1) To expedite time to Market
(faster time to market = higher customer satisfaction = more funding = job security)
2) To reduce Miscommunications
3) Visual depictions of requirements offer a faster intake/ uptake of information
(The Human Mind was designed to think in images not words)
(A picture is worth a thousand words)
4) To reduce the number of meetings
(less meetings = higher productivity = faster time to market)

3. 2
Why LEAN & Testable Stories? (cont’d)
To Align with these Agile Principles and Practices:
• Individuals and interactions over processes and tools
• Working software (or product) over comprehensive documentation
• Our highest priority is to satisfy the customer through early and continuous
delivery of valuable software (or product).
• Welcome changing requirements, even late in development. Agile processes
harness change for the customer's competitive advantage.
• Business people and developers must work together daily throughout the project.
• Deliver working software frequently, from a couple of weeks to a couple of
months, with a preference to the shorter timescale.

4. 3
Typical User Story Layout
Example user story
Size
3
Prio.
High
As a conference attendee..
I want to be able to register
online..
so that I can register quickly
and cut down on paperwork
Acceptance Criteria
Given it is mandatory that I attend the
conference,
When I attempt to register in advance,
Then I would like to get an email with a
confirmation number, to present to my
boss.

5. 4
What is Cucumber Acceptance Criteria?
ILLUSTRATIVE
Example user story
Size
3
Prio.
High
As a conference attendee..
I want to be able to register
online..
so that I can register quickly
and cut down on paperwork
Acceptance Criteria
Given it is mandatory that I attend the
conference,
When I attempt to register in advance,
Then I would like to get an email with a
confirmation number, to present to my
boss.

6. 5
Excellent Model of a Succinct Testable User Story

7. 6
Why LEAN & Testable Stories?
1) To expedite time to Market
(faster time to market = higher customer satisfaction = more funding = job security)
2) To reduce Miscommunications
3) Visual depictions of requirements offer a faster intake/ uptake of information
(The Human Mind was designed to think in images not words)
(A picture is worth a thousand words)
4) To reduce the number of meetings
(less meetings = higher productivity = faster time to market)

8. 7
Visual Examples of a Story’s LEAN Supporting Documentation
Think
Different
Light on Textual depictions heavy on Visual Aids