Doing agile by book is ok for the beginning. However, it's not enough. You should continue to learn by gaining new knowledge during the project. User stories and the way you're working with them are the bricks which form the foundation the better experience. User Stories could be Your best partner and support in project, yet them could become your worst nightmare. Where and how User Stories help? When and how User Stories could become a large burden? Next time we will dig into user story deeper. How it differs from requirements, use cases or test cases? From what parts it consists and why?

1. Vladimir Tarasow
Andris Bariss
The Nuclear Power
User Stories

2. Vladimir Tarasow
About: http://about.me/netrat
E-mail: netrat@netrat.eu
Andris Bariss
About: lv.linkedin.com/in/andrisbariss
E-mail: andris.bariss@gmail.com

3. Product Vision
Describes why the project is undertaken.
Describes what the desired end-state is.
Shared by the Stakeholders, the Product
Owners, the Team and the end users.

4. Requirement
Represents a need.
Must answer the questions What? and Why?
Tries to identify with a clear sentence
what is the problem to solve.

5. User Story

6. User Story Example

7. Card

8. Conversation

9. Confirmation

10. User Story
Represent a description of a “solution” —
from a functional point of view.
Should cut through all the layers of
the architecture.
Must contain also Acceptance Criteria that
describes how the user of the story would
accept the implemented functionality.

11. User Story Template
As a <type of user>
I want to <some goal>
so that <some reason>

12. INVEST Model
Independent. Easier to plan, if it has no
dependencies.
Negotiable. Details added via collaboration.
Valuable. Provides value to the customer.
Estimable. If it's too big or too small, you
can't estimate it.
Small. Can be done in less than a week by
the team.
Testable. Good acceptance criteria.

13. Ready are you?
What know you
of ready?

14. Definition Of Ready
User story is clear enough to start it.
User story can be confirmed.
User story is small enough to fit an
iteration.

15. Acceptance Criteria
High-level criteria from the perspective of
the user or stakeholder.
Define the boundaries for a User Story.
Answer the question: How we will know
when we are done?
Or answer the question: How to demo?
Help developers and testers to derive tests
There are Positive and Negative criteria.

16. Acceptance Criteria Template
Given <context>
When <action>
Then <expected result>

17. Acceptance Criteria Example
As an internet banking customer
I want to see a rolling balance for my everyday accounts
so that I know the balance of my account after each transaction
is applied
ACs:
● The rolling balance is displayed correctly
● The rolling balance is calculated correctly for each
transaction
● The balance is displayed for every transaction for the full
period of time transactions are available
● The balance is not displayed if a filter has been applied

18. When do you know you‘re done?
A Release is done when it satisfies all the
criteria the Product Owner requires to ship
software to production.
A User Story is done when it meets the
story acceptance criteria and the team’s
quality standards for being potentially
shippable

19. Definition Of Done
Applies to all User Stories.
Is the result of an agreement between the
Product Owner and the team on quality.
Should be build in every single piece of
flow — User Story, task…

20. Definition Of Done Example
No (known) bugs.
Passed unit tests.
Passed automated acceptance tests.
Passed user acceptance testing.
Code peer reviewed (if not pair
programmed).
Any build/deployment/config changes
documented/communicated.
Relevant documentation updated.

21. Thank You!
Please, leave feedback!
http://spkr8.com/t/23051

22. Materials used in the presentation:
● 'Advantages of the “As a user, I want” user story template' by Mike Cohn
● 'Definition of Ready' by Ken Power
● 'Essential XP: Card, Conversation, Confirmation' by Ron Jeffries
● 'On Acceptance criteria for user stories' by Sandy Mamoli
● 'What’s Done is Done: User Stories' by Daniel Gullo
● 'User Stories, Epics and Themes' by Mike Cohn
● Master Yoda by ~N68CAL
● Photo by Wexner Center
● Photo by Paul McCarthy
● Photo by Pavel Krok
● Photo by Honou
● Illustrations by Vladimir Tarasow
Credits

23. This work is licensed under the Creative Commons Attribution-
NonCommercial-ShareAlike 3.0 Unported License. To view a copy of this
license, visit http://creativecommons.org/licenses/by-nc-sa/3.0/.