Feedback loops

Each level learns from the level below and from the customer.

01What it's for

The system works because every level learns from the level below and from the customer. Team increments feed the Sprint Review, the ART increment feeds the System Demo, and customer evidence feeds Portfolio Sync. Every level runs the same five events (Refine, Plan, Sync, Review and Retrospect), scaling Scrum's pillars of transparency, inspection and adaptation.

The cadence sets the rhythm: day and two weeks for teams, week, four weeks and quarter for the ART and the portfolio.

02What it turns into on the old system

The flow becomes one-way and top-down: strategy, plan, execution, report. Feedback travels upward only as status, and decisions at the top are not changed by what teams learn.

03How you notice

Portfolio decisions don't change when the evidence does.
The loops have no owner and feed no decision.
What is measured is output, not outcome.

04How to make it work

Give every loop evidence, an owner and the decision it feeds.

Decide as late as responsibly possible, at the lowest level where the best information is.

Escalate only what cannot be decided there, and send the decision back down with the authority to act on it.