Skip to content

Commit 9b27e90

Browse files
committed
GLS edt MBPM completed.
1 parent 486a96a commit 9b27e90

File tree

1 file changed

+40
-39
lines changed

1 file changed

+40
-39
lines changed

docs/slides/content/metrics-based-process-mapping.md

Lines changed: 40 additions & 39 deletions
Original file line numberDiff line numberDiff line change
@@ -7,15 +7,15 @@ TL500 <!-- {.element: class="title-color"} -->
77

88
### Batch Processing
99
#### _What is it?_
10-
* Concurrent work being done
11-
* Typically performed on a schedule or specific timeframe
10+
* Work is done concurrently
11+
* Typically performed on a schedule or within a specific time frame
1212

1313
#### _How can it be used?_
14-
* Help identify Work In Progress limits
15-
* Show flow of work through the team/system
14+
* Helps identify Work In Progress limits
15+
* Shows the flow of work through the team or system
1616

1717
#### [The Penny Game](https://www.leanagiletraining.com/better-agile/agile-penny-game-rules/)
18-
1. Break out into teams and experiment with batch processing using poker chips.
18+
1. Break out into teams and experiment with batch processing by using poker chips.
1919
2. Follow the facilitator's instructions.
2020

2121

@@ -36,21 +36,21 @@ TL500 <!-- {.element: class="title-color"} -->
3636

3737

3838
### Value Streams
39-
Each table picks a sector and a business use case (some examples below):
39+
Each table picks a sector and a business use case, for example:
4040
* **Telco** - Ordering a new Broadband package
41-
* **Finance** - Creating new Current Account
42-
* **Government** - Paying for Council Tax
43-
* **Energy** - Switching energy provider
41+
* **Finance** - Creating new account
42+
* **Government** - Paying a Council Tax
43+
* **Energy** - Switching energy providers
4444

45-
#### Some questions to lead the discussions ...
45+
#### Some questions to lead the discussions:
4646
What is the trigger for the stream?
4747
What is end business value?
4848
What are all the steps in between?
49-
What's the Technology or system that helps with that step?
49+
What are the technologies or systems that help with these steps?
5050

5151

5252

53-
_DevOps is focused on speeding up that value chain. Metric-Based Process Mapping (MBPM) is a practice that will help visualize all these steps and capture some metrics about how long they take._
53+
_DevOps is focused on speeding up the value chain. Metric-Based Process Mapping (MBPM) is a practice that helps visualize all these steps and capture some metrics about how long they take to complete._
5454

5555

5656

@@ -78,21 +78,21 @@ The second generation from Learning to See.
7878

7979

8080
#### _Why use it?_
81-
* Holistically analyze and optimize "brownfield" delivery processes, including everything from requirements definition, infrastructure provisioning and application development.
82-
* Visually represent the way work flows through an organization
83-
* Building a shared understanding throughout the various levels of an organization
84-
how the work is actually done.
85-
* Formulating specific, data driven improvement plans.
81+
* Holistically analyze and optimize "brownfield" delivery processes, including everything from requirements definition to infrastructure provisioning and application development.
82+
* Visually represent the way work flows through an organization.
83+
* Build a shared understanding throughout the various levels of an organization
84+
about how the work is actually done.
85+
* Formulate specific, data driven improvement plans.
8686

8787

8888

8989
### Metrics of Velocity
9090
![accelerate](images/mbpm/accelerate-book.png)<!-- {.element: class="" style="border:none; box-shadow:none; height:200px; float:left;"} -->
9191

9292
* Frequency of deployments (more frequent is better)
93-
* Lead time for new features: from ideation through delivery (shorter is better)
93+
* Lead time for new features from ideation through delivery (shorter is better)
9494
* Frequency of change failures (fewer changes are better)
95-
* Mean-time-to-repair, MTTR (shorter recovery times are better)
95+
* Mean-time-to-repair, or MTTR (shorter recovery times are better)
9696

9797

9898

@@ -101,8 +101,8 @@ how the work is actually done.
101101

102102

103103
#### Flow Metrics
104-
* **Throughput** — the number of work items finished per unit of time
105-
* **Work in progress (WIP)** — the number of work items started but not finished. The team can use the WIP metric to provide transparency about their progress towards reducing their WIP and improving their flow
104+
* **Throughput** — the number of work items finished per unit of time.
105+
* **Work in progress (WIP)** — the number of work items started but not finished. The team can use the WIP metric to provide transparency about their progress towards reducing their WIP and improving their flow.
106106
* **Cycle Time** — the amount of elapsed time between when a work item starts and when a work item finishes.
107107
* **Work Item Age** — the amount of time between when a work item started and the current time. This applies only to items that are still in progress.
108108

@@ -131,7 +131,7 @@ How To ...
131131

132132

133133
### Metric-Based Process Mapping
134-
Document all activities / steps (the things)
134+
Document all activities and steps (the things)
135135

136136

137137

@@ -183,29 +183,29 @@ Document all activities / steps (the things)
183183

184184

185185

186-
#### Summary of the steps
187-
1. Label the map and create Swim Lanes
188-
2. Add time
189-
3. Add the activities (the steps) to the map (some could be in parallel)
190-
4. Document all the activities (the steps). On each sticky note track the activity
186+
#### Summary of the Steps
187+
1. Label the map and create Swim Lanes.
188+
2. Add time.
189+
3. Add the activities (the steps) to the map (some could be in parallel).
190+
4. Document all the activities (the steps). On each sticky note track the activity:
191191
* Name the activity and who's involved
192192
* Add the number of people
193193
* Add the Accuracy (% complete and accurate)
194194
* Add process / Lead Time
195195

196196

197197

198-
### What to do next?
199-
* Identify handoffs
198+
### What To Do Next?
199+
* Identify hand-offs
200200
* Create summary metrics
201201
* Identify improvement areas
202202
* Validate the improvements with a future state MBPM
203203

204204

205205

206206
### Exercise
207-
#### As a class:
208-
1. Walk through the *as-was* MBPM
207+
#### As a class
208+
1. Walk through the *as-was* MBPM.
209209

210210

211211

@@ -215,7 +215,7 @@ Document all activities / steps (the things)
215215

216216
#### In your team
217217
![activity-mbpm](images/mbpm/activity.png) <!-- {.element: class="inline-image"} -->
218-
1. Identify improvements on the steps and if it's possible to reduce handover or remove any of the existing steps.
218+
1. Identify improvements to the steps and whether it's possible to reduce hand-offs or remove any of the existing steps.
219219
2. Document any new activities (the steps). On each sticky note track the activity:
220220
* Name the activity and who's involved
221221
* Add the number of people
@@ -249,12 +249,12 @@ Document all activities / steps (the things)
249249

250250

251251
### Facilitation Tips
252-
* You can map the MBPM steps with the Big Picture flow and improvements for a better visualisation of work
253-
* Use a spreadsheet to calculate numbers for metrics, it will be much easier to do it
254-
* Iterate Iterate Iterate! Start with small teams and compare over and over again
255-
* If psychological safety is low, postpone gathering the numbers until trust there
256-
* Tools with numbers on them can be very intimidating to people
257-
* Don't be too specific about the numbers, just use them as a gauge. It's not about the seconds it's bigger than that
252+
* You can map the MBPM steps with the Big Picture flow and improvements for a better visualization of work.
253+
* Use a spreadsheet to calculate numbers for metrics because it's much easier.
254+
* Iterate Iterate Iterate! Start with small teams and compare over and over again.
255+
* If psychological safety is low, postpone gathering the numbers until trust is established.
256+
* Tools with numbers on them can be very intimidating to people.
257+
* Don't be too specific about the numbers, just use them as a gauge. It's not about the seconds, it's bigger than that.
258258

259259

260260

@@ -267,7 +267,8 @@ Related practices:
267267
* [Team Topologies](https://teamtopologies.com)
268268

269269
There are other practices in the space of working on how we might start building a solution that fixes problems or realize some new opportunities:
270-
270+
<!--I commented on this phrasing elsewhere, it is very ambiguous and wordy. "in the space of working on how we might start building..." I suggested "Suggest "There are other practices to consider as we start building a solution to fix the problem and these can help us recognize new opportunities." in the event-storming module.
271+
Also this para is weirdly indented by a single space-->
271272
* [Emerging Architecture](https://openpracticelibrary.com/)
272273
* [NFR Map](https://openpracticelibrary.com/practices/non-functional-requirements-mapping)
273274
* [Event Storming](https://openpracticelibrary.com/practices/event-storming)

0 commit comments

Comments
 (0)