The AOS seen as a loop chain of services

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

The network is balanced by adjustments to the workflow in timely manner through policies and resources.

From a service point of view (clock wise): Portfolio Mgt. serves Product Mgt. that serves Delivery Mgt., that serves the business through Release Mgt.

From a needs point of view (counter clock wise): Business needs are met through Release Mgt by Delivery Mgt., whose needs are met by Product Mgt., whose needs are met by Portfolio Mgt.

Another way of looking at value delivery: Business Mgt. through Release Mgt., delivers direct to the client, facilitated by both Product Mgt. and Delivery Mgt.

Unknown's avatar

Author: Mario Aiello

Hi, I’m Mario – retired agility warrior from a major Swiss bank, beyond agile explorer, lean thinker, former rugby player, and wishful golfer. I’ve been in the agile space since 2008. I began consulting in 2012 with a Scrum adoption in a digital identity unit — and that path eventually led me to design an Agile Operating System at organisational scale. What pushed me further was frustration: poor adoption, illusionary scaling, and “agile” that looks busy but doesn’t improve business outcomes. That’s why I developed the Adaptive Fitness System (AFS) — an approach that treats agility as fitness for change: fit for purpose, fit for context, fit for execution, and fit for continuous improvement. Today, I use AFS to help organisations sense what’s real, learn fast, and adapt with intent.