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
A tool to capture and articulate the non-functional requirements of a solution that a team are striving to deliver
29
+
A tool to capture and articulate the non-functional requirements of a solution that a team is striving to deliver
30
30
31
31
<br>
32
32
@@ -41,9 +41,9 @@ A tool to capture and articulate the non-functional requirements of a solution t
41
41
42
42
43
43
#### Why do we use it?
44
-
* To gain a shared understanding of non-functional aspects of a system in a visually structured representation.
44
+
* To gain a shared understanding of the non-functional aspects of a system in a visually structured representation.
45
45
46
-
* On completion you should have a good view on the key non-functional considerations for the solution and where work is required to realise these.
46
+
* On completion, you should have a good view on the key non-functional considerations for the solution and the work required to achieve them.
47
47
<!--
48
48
--->
49
49
@@ -55,22 +55,23 @@ A tool to capture and articulate the non-functional requirements of a solution t
55
55
56
56
57
57
#### How do we do it?
58
-
1. Ensure that everyone participating is comfortable with the headings and what they mean <!-- .element: class="fragment" -->
59
-
2. For each heading, capture on stickies important considerations or requirements for the system or solution. Depending on the number of participants, you could use facilitation techniques such as 1-2-4-all or splitting into smaller groups to capture items <!-- .element: class="fragment" -->
58
+
1. Ensure that everyone participating is comfortable with the headings and what they mean.<!-- .element: class="fragment" -->
59
+
2. For each heading, capture important considerations or requirements for the system or solution on sticky notes. Depending on the number of participants, you could use facilitation techniques such as 1-2-4-all or splitting into smaller groups to capture items.<!-- .element: class="fragment" -->
3. For each heading, play back the stickies as a group <!-- .element: class="fragment" data-fragment-index="0" -->
66
+
3. For each heading, play back the stickies as a group. <!-- .element: class="fragment" data-fragment-index="0" -->
67
+
<!--TechEdit: "play back" seems an odd action for a sticky note, it's more for a video or recording. If participants are reading the stickies out, say "read out" or "read aloud"; "For each heading, read the sticky notes aloud as a group." This phrasing is used again later so if changed here we should change all.-->
67
68
4. During the playback, think about whether each sticky should be: <!-- .element: class="fragment" data-fragment-index="1" -->
@@ -80,25 +81,26 @@ A tool to capture and articulate the non-functional requirements of a solution t
80
81
81
82
82
83
#### Setting the Scene: Pet Battle Industries
83
-
Pet Battle Industries have a good handle on the functional design of their applications. Let's not think of all the _other_ things they need to do to harder their application.
84
+
Pet Battle Industries has a good handle on the functional design of their applications. Let's not think of all the _other_ things they need to do to harder their application.
85
+
<!-- Tech Edit: I think this should be "Now, let's think of all the _other_ things they need to do to harden their application." Please confirm. -->
84
86
85
87
86
88
87
89
88
90
### Create the NFR Map
89
-
#### *As a class:*
91
+
#### *As a class*
90
92
91
-
1. Ensure that everyone participating is comfortable with the headings and what they mean
92
-
2. Split the map into two segments and divide among the teams - each team taking at least one half of the map
93
-
#### *In your team:*
94
-
3. For your area: for each heading, capture important considerations or requirements for the system or solution and add stickies for each item
93
+
1. Ensure that everyone participating is comfortable with the headings and what they mean.
94
+
2. Split the map into two segments and divide among the teams - each team taking at least one half of the map.
95
+
#### *In your team*
96
+
3. For each heading in your area, capture important considerations or requirements for the system or solution and add sticky notes for each item.
95
97
96
98
97
99
98
100
# Exercise Wrap Up
99
-
#### *As a class:*
100
-
3. Merge the Map with all area
101
-
4. For each heading, play back the top two or three stickies as a group
101
+
#### *As a class*
102
+
3. Merge all the map areas together.
103
+
4. For each heading, play back the top two or three sticky notes as a group.
102
104
5. During the playback, think about whether each sticky would update the DoD / ACs on a story or form an experiment for the sprint.
103
105
104
106
@@ -114,11 +116,11 @@ Pet Battle Industries have a good handle on the functional design of their appli
114
116
115
117
116
118
### Facilitation Tips
117
-
As you review items on the map define if any sticky note could be:
119
+
As you review items on the map, define if any sticky notes could be:
118
120
119
-
-added to the backlog and prioritized as it requires work to realize
120
-
-be included in the Definition of Done
121
-
-be part of the acceptance criteria for any backlog items
121
+
-Added to the backlog and prioritized because it requires work to realize
122
+
-Be included in the Definition of Done
123
+
-Be a part of the acceptance criteria for any backlog items
0 commit comments