The purpose of prioritising The Rules and The Agile Value Streams is to allocate resources more effectively.
Priority can determined in multiple ways, for example:
- What would our Agile Customers like us to focus upon first?
- Which Internal Challenges would we like to resolve first?
- Which Rules and Agile Value Streams do we consider quick-wins?
- aka low-hanging fruit (an approach often used to gain momentum)
- Which Rules and Agile Value Streams offer the highest value?
- Although, perhaps not the cheapest, or easiest to achieve
6.5.1 How to prioritise The Rules and The Agile Value Steams
Once we have considered the options, and confirmed resource availability, we can then implement The Rules and The Agile Value Streams in the sequence we have defined.
In the example below, the Enablers will focus upon Minimising Waste first. This is common for existing Products/Services that are known to have waste.
Second, the Enablers have decided to review their Shared Vision. Perhaps there is not one in place at the Product/Service-level, or perhaps there is, but it needs some refinement.
Third, the Enablers have decided to review the Product/Service-specific value streams to help achieve the various Time to Value (aka Speed) targets.
6.5.2 How long will it take to implement one Rule and it’s Agile Value Stream?
Whilst a specific answer is impossible. We’d expect a maximum of 3 months. Any longer, and it probably indicates that an Enabler is not actually fulfilling their role correctly.