
This booklet is an updated version of the Agile Operating System, developed for a multi-value stream business unit, and implemented in their quest for business agility.

This booklet is an updated version of the Agile Operating System, developed for a multi-value stream business unit, and implemented in their quest for business agility.

In a generative model we learn about needs by exploring the context, figuring out what knowledge will enable the right changes.
Continue reading “The AOS seen as a generative agility model”
The Agile Operating System facilitates the scaling of an agile transformation by promoting suatainable business agility . Sustainable agility and meaningful change relies on an ecosystem that supports new ways of working that extend from the team level to the executive level.
Continue reading “The AOS supports Business Agility”
The Agile Operating System (AOS) addresses the value stream of an organization by identifying the relevant workflows that intervene in the business value creation process.
Continue reading “The AOS revisited”
The Kanban Lens
In his blog Andy Charmichael defines the Kanban lens as follows:
The Agile Operating System (AOS) can be then analized through this lens as follows:
Continue reading “The AOS through the Kanban lens”
See the Agile Operating System (AOS) as a consensual chain of inter connected services:
– The AOS is a chain: sequence of services linked through feedback loops
– The AOS is consensual: work agreed is decomposed and handled by adjacent level service
– The AOS is inter-connected: blockers on work items affect other services
Handoffs are a sort of waste (they represent the transition from one ownership level to another, the equivalent to transportation as a sort of manufacturing waste) and the Lean nature of the Agile Operating System (AOS) aims at preventing waste.
Are there any handoffs within the AOS, and how are they dealt with?
The answer is NO!
Continue reading “The AOS and handoffs”
This analysis is inspired by Mike Burrows Right to Left thinking, which I found pertinent to apply it to the Agile Operating System (AOS) as the model is lean in nature and it focuses on the value outcome to the client.
Continue reading “The AOS: Right to Left”
The Agile Operating System (AOS) life span consists of three moments: learn and adapt; try and adopt; reflect and improve.
Continue reading “The AOS adoption pattern”The Agile Operating System (AOS) promotes a model in which structure and workflow are the main components. Continue reading “AOS: agile organization and workflow”
The Agile Operating System (AOS) value chain is composed of a series of backlogs, i.e. Enterprise BL, Product BL, Release BL, Iteration BL and Technical BL, all of these granting the cohesion of the value delivery. Continue reading “Value chain completeness guide within the AOS”

The Agile Operating System (AOS) is a global enterprise model, powered by continuous improvement approach to both the how and why things are done, and launched by a collection of alternative agile practices that drive the teams value delivery approach. Continue reading “AOS Analysis”
The Agile Operating System (AOS) is about Agile Discovery, Agile Delivery, and Agile Facilitation. Continue reading “AOS description”
The organization’s reasons and motivation to follow the agile way will shape the transition towards agility; which in general is driven by some sort of business outcome. The Agile Operating System (AOS) is a model designed to enable an organization’s agile evolution. Continue reading “Agile transition through the AOS”
“Essentially, all models are wrong, but some are useful.” – George Box, 1976
The enterprise Agile Operating System (AOS) is an engagement model designed to improve the organization’s way of work by encouraging behavioral change in line with Agile/Lean principles. Continue reading “The Agile Operating System – AOS”