Presentation about going beyond writing the first user stories and identifying when a user story can be too big, too vague, etc.

1. User Stories
Deep Dive

2. User Stories

3. Focused on what
(not how)

4. What you expect
(avoid being vague)

5. Manage scope
(lightweight)

6. Don’t include many
details(Details will come later)

7. It can be estimated
(otherwise is too big)

8. It should fit in a card
(or sticky note)

9. It’s not a contract
(it will change)

10. Placeholder for
conversation

11. Where do User
Stories live?

12. User Story Map
R1
R2
User
Activities
User Tasks
User Stories
User Stories

13. Kanban
Backlog Analysis Coding QA Deploy

14. Writing user stories

15. Format I
As a [ROLE]
I want to [ACTION]
So I can [GOAL]
Who
What
Why

16. Format II
In order to [GOAL]
As a [ROLE]
I want to [ACTION]
Who
What
Why

17. INVEST guideline

18. Independent

19. Negotiable

20. Valuable

21. Estimable

22. Small

23. Testable

24. Non Functional
Requirements

25. Make it part of a
story
(if possible)

26. Write a test

27. Even a manual test

28. Make sure there’s
some kind of card
on the board

29. No matter the format

30. What about the
details?

31. When is the right
time to add details?

33. When can more
stories be
discovered?

34. Any time!
Anywhere!

35. Examples

36. Movie Library App
Donald likes to watch movies and tell his
friends about it. He uses a site that helps him
to find movies (old, new, etc), rate them and
share with others.
He also enjoys the previews and loves to hear
when his “favourites” movies are playing in
theatres.

37. Right or Wrong?
As a Developer
I want use a NoSQL db to store movies
So I can list them faster

38. Right or Wrong?
As a Developer
I want to use Twitter Bootstrap for the
UI
So I can use all the cool buttons and
layout

39. Right or Wrong?
As a User
I want my app to be easy to use
So I can get the top ten UIX award

40. Right or Wrong?
As a User
I want to get statistics about movies
So I can decide which users could be
willing to buy a movie ticket ahead of
time

41. Right or Wrong?
As a User
I want to login to the site
So I can use the site

42. Right or Wrong?
As a User
I want to login to the site but if I forget
my password I want a password recovery
email or maybe use Google instead
So I can review movies

43. English Master
EnglishMaster is an application to let users
read lessons to learn and improve english.
The lessons are provided in an alphabetical
index that the user can filter by choosing a
letter of the alphabet or searching for a word.

44. Medical Studies
The application needs to process XML files contains
medical studies that come with patient information
and study results.
The studies are uploaded in a Zip file to our FTP
server. Each new file needs to be processed and
added to the database (unless it has been
processed).
It is important to be robust and handle errors to
avoid duplication.

45. Sizing stories

46. Identify Complexity

47. Task Breakdown

48. Throwing a dice

49. ShakingTwo
Months

50. User Story Points
Using Fibonacci (1, 2, 3, 5, 8, 13 …)

51. Planning poker

52. Benefits &
Drawbacks

53. Relative complexity

54. Tend to average

55. How often do we
estimate?

56. Can we avoid
estimation?

57. It will take what it
takes?

58. Let’s make each
story…

59. Around the same
size

60. The path to…

61. NO ESTIMATES!

62. Acceptance Criteria

63. When are we done?

64. Writing Scenarios
Input
Output
Step 1
Step 2
…
Step N

65. Multiple Scenarios

66. Gherkin DSL
Business readable DSL
Flush out requirements
Automated testing
Used by Cucumber, SpecFlow,
jBehave

67. Features
Feature: Listing movies
As a User
I want to list movies
So I can see the contents of the library

68. Scenarios
Scenario: List all movies
Given I'm logged in
And I have (some data loaded)
When I (do some action)
Then I (should see expected results)

69. Writing reviews
Scenario: Write a review for a movie
Given I'm logged in as a Critic
When I write a review for a movie
Then I should see the new review
in the reviews section
for the movie

70. Example II
Scenario: See most recent movies first
Given I'm logged in as a User
When I order the list by release date
Then I should see the movies with the
release date most recent first

71. Guidelines to
write
scenarios

72. ??????
Scenario: Perfect world
Given the application is setup
When I want to use some projects
Then I should be able to load data
And have a great user experience
but no bugs should appear

73. ?????
Scenario: Redirect user
Given a User "dave" with pwd "secret"
And I am not logged in
When I navigate to the home page
And I fill in "Username" with "dave"
And I fill in "Password" with "secret"
And I press “Login"
Then I am redirected to the login form

74. Just right
Scenario: List all projects
Given I'm logged in
And I have some projects stored
When I list the projects
Then I should see all of them

75. Estimating
using scenarios

76. More Functionality
When is the right time to write scenarios?
During Inception?
During Analysis?
During Development?
During QA?

77. Order Matters Not!
Can every feature be independent?

78. Size Matters not!
Can every story be of the same size?

79. Complexity ∝ amount
How many scenarios per feature?

80. Complexity ∝ amount
The more scenarios we find the more
complex the story is

81. Complexity ∝ amount
If scenarios are unclear, then is time to
rethink the feature

82. Complexity ∝ amount
Scenarios
0
1
2
4
5
6
7
Complexity
Simple Medium Complex WTF?

83. Complexity ∝ Clarity
Too many steps

84. Complexity ∝ Clarity
Takes more than 10 minutes to write

85. Complexity ∝ Clarity
You read it the next day and
have no clue what it means

86. Recipe
Make every story around the same size

87. Recipe
One or two scenarios most

88. Recipe
Make sure you can implement it in XX
amount of time
(1 or 2 days)

89. Recipe
Find the simplest scenario
that provides value

90. THANK YOU!

91. The Smartest tool
for agile project
management
http://smartview.io

92. amir@barylko.com
@abarylko
http://bit.ly/abarylkoslides
http://orthocoders.com
http://westerndevs.com