Changing How You Build

Marty Cagan and Jon Moore argue that a product-led company's engineering practices should rest on three principles: protecting customers, revenue, brand and colleagues; responding quickly to market needs; and earning customer trust through reliable delivery. They say the main technique for all three is small, frequent, reliable releases, supported by serious investment in test automation and quality assurance. They contrast this with 'big bang' releases, which cause long delays, customer disruption and eroded trust. Finally, they note that Agile rituals alone don't produce this capability; what matters is the actual release cadence, which many strong teams achieve through continuous integration and deployment without formal Agile processes.

01Key takeaways

• Judge your delivery capability by how often you actually ship, not by how many Agile ceremonies you run.
• Invest in test automation and deployment automation to make small, frequent releases safe.
• Keep changes small so that regressions are easier to detect and their causes easier to find.
• Build the ability to diagnose, fix, test and deploy urgent issues quickly, since customers judge you on response speed.
• Treat reliability of commitments as a trust-building asset and deliver what you promise, when you promise it.
• Recognize that frequent small releases also reduce disruption for customers compared with large periodic changes.

02Key sections

Three core principles

Good product building protects customers and colleagues from breakage, lets teams respond fast to market and regulatory changes, and keeps commitments that build customer trust.

Small, frequent, reliable releases

The core technique is releasing often, from at least every two weeks up to several times a day, which makes quality easier to verify and problems easier to trace.

Testing new capabilities and regressions

Teams must verify that new features work and that changes don't break existing behavior, which requires heavy test automation and small change sets.

The cost of big bang releases

Infrequent, massive releases create weeks or months of stabilization, overwhelm customers with change, and often lead customers to demand even slower releases.

Agile is not the goal

Agile methods helped many firms reach frequent releases, but the real test is release cadence; continuous integration and deployment can be achieved without formal Agile processes.

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.