SAFe · apply · about 10 minutes

The reorganisation that kept the org chart

A 300-person engineering organisation has adopted SAFe. It has three "ARTs": Front End, Platform, and Data — each about 100 people, matching the three existing departments and their three directors. PI Planning runs for two days a quarter and mostly produces a dependency board with 60-odd red strings between the trains. The RTEs spend each PI renegotiating those dependencies. Business Owners attended the first PI Planning and have sent delegates since. The CTO says SAFe is "working but heavy" and asks whether to add Portfolio SAFe to get better oversight. You have one meeting.

Say what is actually wrong, and answer the Portfolio question. Be direct — they are not asking to be told they failed.

Write your answer somewhere else — on paper, in a mail draft, out loud to someone. Then come back and mark it against the rubric. The rubric is disputable: if you think a line is wrong for your situation, you are probably right, and noticing that is worth more than the tick.

Mark it against the rubric

Names the real fault: trains drawn around departments, not development value streams Operational and development value streams
Explains the 60 dependencies as the symptom — component trains must cross each other to deliver anything A long-lived team of Agile teams
Answers the Portfolio question with no: more governance over the wrong structure adds cost, not oversight Four configurations, and Essential is the floor
Flags the delegated Business Owners as a lost control rather than a diary problem Business Owners carry the ROI
Reads the RTEs' renegotiation as the role drifting into programme management The RTE is a coach, not a programme manager
Proposes re-cutting one train around a value stream as evidence, rather than a full re-org Long-lived is the load-bearing word

Sources: SAFe Glossary (Scaled Agile, Inc.), Scaled Agile Framework, What's new in SAFe? — the framework's own change log. Written from those texts and last checked on 2026-10-16 against reporting on them — not read line by line against the primary documents. Every card names the clause it comes from precisely so you can settle it at the source, and [email protected] is where a correction goes.

SAFe® and Scaled Agile Framework® are registered trade marks of Scaled Agile, Inc. ytyk.org is not affiliated with, endorsed by or licensed by Scaled Agile, Inc. These cards are independent commentary written in our own words; no SAFe text, graphic or Big Picture is reproduced here.