Scaling Agile FAQ

Marty Cagan follows up on his critique of SAFe, the scaled-agile framework, by answering reader questions. He argues that process choices are really culture choices, and that adopting a heavy framework signals top-down control and a misunderstanding of how to compete. He points to Google, Amazon and Netflix as proof that large companies can succeed by hiring strong people and empowering them, without heavyweight process. He also stresses that tools are never neutral, since they encourage particular ways of thinking, and that the real issue is the project mindset versus the product mindset. The piece matters because companies that adopt process over empowerment risk losing their ability to compete with technology-driven rivals.

01Key takeaways

• Treat any process adoption as a cultural signal about how leaders value engineers, designers and product managers.
• Be skeptical that tools and frameworks are neutral; each one encourages particular ways of working.
• Large enterprises can compete by hiring strong people and empowering them rather than adding heavy process.
• Use a process as a means to outcomes, watching for the common trap of tracking process compliance instead of results.
• Distinguish the project mindset (delivering scope) from the product mindset (solving customer problems), and aim for the latter.
• Regulated industries can still adopt modern product practices; constraints do not require heavyweight frameworks.

02Key sections

Process is culture

Cagan says choosing a framework like SAFe is a loud statement about how leaders view engineers, designers and control. He suggests it reveals whether leaders understand what competing with companies like Amazon requires.

Scrum versus SAFe as a first step

Strong teams often start with Scrum and then evolve to leaner practices, but SAFe is too big and heavy to serve as a sensible stepping stone. He has not seen anyone progress from SAFe to a product mindset.

Enterprise scale without heavy process

Google, Amazon and Netflix operate at massive scale and under constraints, yet they rely on hiring skilled people and empowering them rather than heavyweight frameworks.

Tools are not agnostic

Frameworks and tools nudge users toward specific behaviors, and even good tools like OKRs can be misused, so teams must check that a tool's intent matches how they want to work.

Project versus product mindset

The project and program mindset, embodied by the PMO, is the core problem, though the delivery management role remains valuable. The product mindset is the alternative, and regulated industries can adopt modern practices too.

03From the post

“A partnership dedicated to teaching best practices to product teams and product leaders”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.