You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a < type of user >, I want < some goal > so that < some reason >
31
-
#### As a learner, I want to stay awake so that I can be attentive and listen to teacher
31
+
#### As a learner, I want to stay awake so that I can be attentive and listen to the teacher.
32
32
33
-
User Story Mapping is an effective practice for creating lightweight release plans that can drive standard Agile delivery practices. At the end of user story mapping, you should have:
33
+
User Story Mapping is an effective practice for creating lightweight release plans that can drive standard Agile delivery practices. At the end of User Story Mapping, you should have:
@@ -46,10 +46,10 @@ User Story Mapping is an effective practice for creating lightweight release pla
46
46
47
47
User Story Mapping
48
48
49
-
* Frame the opportunity, goal, outcome, and value
50
-
* Tell the story of the product from left to right (user steps)
51
-
* Go back and talk about and capture the details of each step
52
-
* Use valuedriven outcomes to slice out valuable release plans
49
+
* Frame the opportunity, goal, outcome, and value.
50
+
* Tell the story of the product from left to right (user steps).
51
+
* Go back to talk about and capture the details of each step.
52
+
* Use value-driven outcomes to slice out valuable release plans.
53
53
54
54
</div>
55
55
</div>
@@ -72,7 +72,7 @@ User Story Mapping
72
72
~ Jeff Patton
73
73
74
74
</br>
75
-
"User Story Mapping is a visualisation tool that drives groups towards a shared understanding."
75
+
"User Story Mapping is a visualization tool that drives groups towards a shared understanding."
76
76
77
77
~ Tim Beattie
78
78
</div>
@@ -81,7 +81,7 @@ User Story Mapping
81
81
82
82
83
83
#### Value Slicing
84
-
_The goal of value slicing is to divide user stories into iterations such that it forms the outline of a plan. Usually the first iteration builds a minimally viable product._
84
+
_The goal of value slicing is to divide user stories into iterations that form the outline of a plan. Usually the first iteration builds a minimally viable product._
85
85
86
86
87
87
@@ -91,24 +91,24 @@ _The goal of value slicing is to divide user stories into iterations such that i
91
91
92
92
93
93
#### _Why use it?_
94
-
* No one likes estimating work effort, but it's an important step in many environments. User Story Mapping presents an approach to estimation that many teams find much more tolerable than practices like planning poker or t-shirt sizing
95
-
* Many projects have a natural progression of work from beginning, middle to end. This progression is often lost in a traditional flat backlog. User Story Mapping captures this information with a lightweight mechanism to plan out more than one iteration (i.e. an Agile release plan)
96
-
* User Story Mapping presents backlog items in the context of the overall business process so you don't lose sight of "the big picture", a common pitfall in Scrum projects
94
+
* No one likes estimating work effort, but it's an important step in many environments. User Story Mapping presents an approach to estimation that many teams find much more tolerable than practices like planning poker or t-shirt sizing.
95
+
* Many projects have a natural progression of work from beginning, middle to end. This progression is often lost in a traditional flat backlog. User Story Mapping captures this information with a lightweight mechanism to plan out more than one iteration (i.e., an Agile release plan).
96
+
* User Story Mapping presents backlog items in the context of the overall business process so that you don't lose sight of "the big picture", a common pitfall in Scrum projects.
1) Follow the **INVEST** guidelines for good user stories
104
-
2) Individually capture, using stickies everything you do in the process you are mappingand add all activities to the story map. Visualise everything
105
-
3) Identify and remove duplicates
106
-
4) Cluster similar activities and capture a theme title
107
-
5) Slice out high value to form incremental release strategy. Filter and maintain focus on delivering valuable outcomes
103
+
1) Follow the **INVEST** guidelines for good user stories.
104
+
2) Individually captureeverything you do in the process that you are mapping, and add all activities to the story map by using sticky notes. Visualize everything.
105
+
3) Identify and remove duplicates.
106
+
4) Cluster similar activities and capture a theme title.
107
+
5) Slice out high value to form an incremental release strategy. Filter and maintain focus on delivering valuable outcomes.
@@ -138,23 +138,22 @@ _The goal of value slicing is to divide user stories into iterations such that i
138
138
139
139
### Class Exercise
140
140
141
-
_What are all the activities you do to in the morning to prepare for work and get there on time?_
141
+
_What are all the activities that you do in the morning to prepare for work and get there on time?_
142
142
143
-
1. As an individual, capture on individual stickies all the things you do from the moment you wake up until you arrive at work<!-- {.element: class="fragment" data-fragment-index="1"} -->
144
-
2. As a team, add all activities to the story map and remove duplicates. If some are similar but slightly different, do not remove as duplicates<!-- {.element: class="fragment" data-fragment-index="2"} -->
145
-
3. Cluster similar activities and capture themes above them e.g. Cleaning Routine<!-- {.element: class="fragment" data-fragment-index="3"} -->
143
+
1. As an individual, capture all the things you do from the moment you wake up until you arrive at work on individual sticky notes. <!-- {.element: class="fragment" data-fragment-index="1"} -->
144
+
2. As a team, add all activities to the story map and remove duplicates. If some are similar but slightly different, do not remove them.<!-- {.element: class="fragment" data-fragment-index="2"} -->
145
+
3. Cluster similar activities and capture themes above them, such as "Cleaning Routine."<!-- {.element: class="fragment" data-fragment-index="3"} -->
146
146
147
147
148
148
149
149
### Class Exercise 🛏 ⏰
150
150
151
-
_Oh no! You slept through your alarm and woke up... now you must get to a big meeting at work that you cannot miss. What activities **must** you do to prepare for work and get there on time? You cannot join remotely!_
151
+
_Oh no! You slept through your alarm and woke up late! Now, you must get to a big meeting at work that you cannot miss. What activities **must** you do to prepare for work and get there on time? You cannot join remotely!_
152
152
153
153
1. As a team, draw a line on the user story mapping board representing what
154
-
must be done<!-- {.element: class="fragment" data-fragment-index="1"} -->
155
-
2. Discuss which stories are absolutely necessary given the scenario 🛏 ⏰ <!-- {.element: class="fragment" data-fragment-index="2"} -->
156
-
3. Move stories below the line that are not absolutely necessary based on
157
-
consensus of the team<!-- {.element: class="fragment" data-fragment-index="3"} -->
154
+
must be done.<!-- {.element: class="fragment" data-fragment-index="1"} -->
155
+
2. Discuss which stories are absolutely necessary given the scenario. 🛏 ⏰ <!-- {.element: class="fragment" data-fragment-index="2"} -->
156
+
3. Move stories below the line that the team agrees are not absolutely necessary.<!-- {.element: class="fragment" data-fragment-index="3"} -->
158
157
159
158
160
159
@@ -186,15 +185,15 @@ consensus of the team<!-- {.element: class="fragment" data-fragment-index="3"}
0 commit comments