Product Strategy in an Agile World

Marty Cagan argues that product strategy has been an unintended casualty of the move to Agile methods, leaving teams chasing features without direction. He defines product strategy as a persuasive, two-to-five-year vision of the benefits and problems a product will solve, not a feature spec. It bridges business strategy and the product roadmap, and it is developed through deep understanding of users, market, and technology. Cagan contends that Agile, applied properly, is fully compatible with a clear strategy and can help realize it faster, since the strategy leaves features and sequencing open to change.

01Key takeaways

• Define a product vision two to five years out that focuses on user benefits and problems solved, not specific features.
• Make sure the product strategy directly supports the business strategy and is not a restatement of it.
• Develop the strategy through research and debate with designers, engineers, stakeholders, and executives.
• Keep the roadmap and feature sequencing flexible while holding steady to the strategic direction.
• Create product principles alongside the strategy to guide everyday trade-off decisions.
• Share the strategy with engineers so they can anticipate future needs in their technology and architecture choices.

02Key sections

The Agile Strategy Confusion

Cagan describes frustrated engineers whose product manager avoided longer-term direction, believing Agile meant staying flexible. He sees this misconception as a common problem.

What a Product Strategy Is

A product strategy is a visionary, persuasive description of the desired outcome over a multi-year horizon, focused on benefits rather than specific features.

Linking Business and Product Strategy

The product strategy connects business goals to the product roadmap, translating a business objective into the product capabilities needed to achieve it.

Developing the Strategy Collaboratively

Good strategy comes from research and debate with designers, engineers, stakeholders, and management, and product managers should proactively propose it rather than wait for it to be handed down.

Strategy Versus Roadmap and Principles

The strategy does not lock in features or sequencing, which stay flexible in the roadmap, and product principles help teams make trade-offs consistent with the strategy.

Why Teams Need the Vision

A shared strategy keeps engineers motivated, builds trust in the product manager, and helps the team anticipate future requirements in technology and architecture choices.

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.