Dual-Track Agile

Marty Cagan argues that Agile product teams often suffer from poorly defined backlog items, slow velocity, rework, and unvalidated ideas. He proposes Dual-Track Agile, which runs a Discovery track to quickly validate ideas alongside a Delivery track that produces releasable software. Rather than passing artifacts sequentially like mini-waterfalls, product managers, designers, and lead engineers collaborate side by side. Validation happens during discovery, often before production code is written, which cuts waste and speeds real business results. The essay also notes that the author later moved to the terms Continuous Discovery and Continuous Delivery because the label encouraged a focus on process over principles.

01Key takeaways

• Treat validation as the highest-order goal and pursue it the fastest, cheapest way possible.
• Run discovery and delivery as parallel tracks rather than sequential phases or handoffs.
• Have the product manager, designer, and lead engineer work together side by side on backlog items.
• Validate ideas with prototypes before writing production code, following the fake it before you make it approach.
• Use prototypes as the delivery spec to reduce rework and ambiguity during sprints.

02Key sections

The Problem with Poorly Validated Backlogs

Agile teams often hold frustrating sprint planning because backlog items are vague, unvalidated, and still being designed mid-sprint. This drives slow velocity, weak design, and heavy rework.

Validate Cheaply Before Building

Building and launching is the slowest and most expensive way to test an idea, so the goal is to validate ideas as fast and cheaply as possible.

Two Parallel Tracks

Discovery generates validated backlog items, while Delivery generates releasable software. The two tracks run in parallel rather than as serialized phases.

Collaboration Instead of Handoffs

The author criticizes mini-waterfalls where each role hands artifacts to the next. In dual-track work, the product manager, designer, and lead engineer collaborate side by side.

Fit with Lean UX

Lean UX suits dual-track work because it focuses on prototypes validated during discovery, and the prototype then serves as the delivery spec.

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.