| commit | author | age | ||
| 339772 | 1 | # Value Stream Mapping and Metric Based Process Mapping |
| TB | 2 | |
| be6b06 | 3 | > Session to introduce the practices of Value Stream Mapping and Metric Based Process Mapping, how we use the and show some examples of real Metrics Based Process Map artefacts. This will also include a short interactive exercise to practice MBPM. |
| 339772 | 4 | |
| TB | 5 | _____ |
| 6 | ||
| 7 | ||
| 8 | ## Slides | |
| 9 | ||
| 10 | The latest version of slides for the session are available [here](https://drive.google.com/open?id=1W6hmobS5o33fllg0Pcfql6-oYWcvkXAXFC5CX8_tvRU) | |
| 11 | ||
| 12 | ||
| 13 | ## Facilitation Materials Needed | |
| 14 | ||
| 49d11e | 15 | * Pennies or poker chips (20 for each table) |
| TB | 16 | * Flipchart paper - one piece for each table |
| 17 | * Marker pens | |
| 339772 | 18 | * Teams in table size of 4 to 6 |
| TB | 19 | * Sticky Notes - set of the following on each table |
| 20 | * Small Rectangular - lots of one color | |
| 21 | * Sharpie Pens (1 per person) on each table | |
| 22 | * Single color Painters' Tape | |
| be6b06 | 23 | * Lots of board / wall space to fit 2 large MBPMs (with 12 people collaborating around) |
| 339772 | 24 | |
| TB | 25 | |
| 26 | ## Facilitation Guidelines | |
| 27 | ||
| 49d11e | 28 | * Play the [Penny Flow game](https://www.leanagiletraining.com/better-agile/agile-penny-game-rules/) to introduce the notion of capturing metrics around flow (and the impact batch size has). |
| TB | 29 | * Present the slides to introduce Value Stream Mapping and Metrics Based Process Mapping, what they are and why we use them. Show some real world examples and talk through the MBPM before and after as well as the roll-up of metric improvements. |
| 30 | * Optiopnnaly, run a further interactive exercise (with the addition of the Penny Flow Game and the feedback before and after including this, this exercise is less valuable): | |
| 339772 | 31 | * In pairs, capture all business processes between the trigger of the business requesting a feature and the outcome of that feature running in production and being used |
| TB | 32 | * In groups of 12, combine all processes onto a single map |
| 33 | * Add some metrics based on traditional software development (with minimal automation) - Process Time, Lead TIme, CAC% | |
| 34 | * Facilitate a playback of each MBPM and start discussing about activities or practices that may help drive improvements | |
| 35 | ||
| be6b06 | 36 | |
