- With the constraint of time our aim is still to realise the full “value” of getting on time to the office. In the process of minimizing the activities, we removed many of them in each step and left the process very thin and lean but still end-to-end.
- Since we have a constraint of time, as we eventually want to be fast which means minimize the time to reach value. in many cases we will go too deep in a single step and not realise the full end-to-end value. in this exercise we demonstrate how it should be done across the map and how in every increment we build we have the full end-to-end.
- We don’t invest equally in each step – in some steps we left only one activity and in some we left more, depending on the step. Some steps where even entirely removed.
- Choosing the depth of each step is easier when the full picture is available since the alternatives are visible.
- Focusing on a single activity but in the context of end-to-end value helps development teams better understand the scope of the requirement. For example, preparing breakfast in the context of getting out of the house in 15 minutes is totally different from preparing breakfast for the family on a vacation morning. Communicating effectively the context helps to make the scope more precise and to trim the less important parts of the scope.