In a generative model we learn about needs by exploring the context, figuring out what knowledge will enable the right changes.
Through the purpose for agility we learn and define the value stream, then learn to generate workflows, learning and identifying responsibilities and how to distribute roles and functions, to learn how to set delivery execution patterns, teaching us to reflect towards continuous improvement, that finally refines the initial purpose.
The AOS can be seen as a generative model, it is descriptive as for what workflows may be needed within the value stream to acheive the purpose of business agility.
The AOS doe not tender to the WHY for agility as this reflection belongs entirely to the organisation in their quest for purpose. What the AOS does is help model the value streams and start the conversations around agility being fit for the business purpose.
There is a phase of learning around value discovery where acceptance and funding of initiatives happen and the Business Backlogs are created.
Having decided on what is the right thing to deliver, the next round of learning involves conversations about value management, designing the right thing (minimum business increments – MBI’s) and when to deliver it, the release plan and the product backlog are the main outcomes of this activity.
These lay the foundations for value delivery, converse, learn and decide how to build the right thing right, to continuously deliver minimum value increments.
Learning, packaging and deploying MBI’s is the main focus of the value release flow of the value stream, where the release plan is executed, where customer needs are satisfied, where business outcomes are materialised.
The generative learnings from the model are carried out within the AOS through the work intake processes that link the workflows of the value stream. Here is where the conversations happen, where needs are understood, outcomes agreed, where work is clarified and accepted.
Agile Ways 