Dual-Track Agile
Discovery and delivery running in parallel
Dual-Track Agile runs two parallel tracks: a discovery track (continuous research and validation to find what's worth building) and a delivery track (engineering sprint cycles to build what's already validated). The PM and designer are always 1–2 sprints ahead in discovery, so engineers are never blocked waiting for decisions.
Coined by Jeff Patton, developed and popularised by Marty Cagan (SVPG) through his books 'Inspired' (2008, 2017) and 'Empowered' (2020).
Use Dual-Track Agile when
- ✓You've been shipping features without validating they solve real problems
- ✓Discovery and delivery are sequential causing long lead times
- ✓PMs want to get closer to customers without slowing down engineering
- ✓The team has the capacity for a designer or researcher to run discovery concurrently
Avoid it when
- ✗Very small teams (1 PM, 1 engineer) who can't run two tracks simultaneously
- ✗Highly constrained products where the solution space is predetermined
Key Concepts
Continuous research, prototyping, and validation work to answer: is this valuable, usable, feasible, and viable?
Engineering sprint cycles building pre-validated features. Work enters delivery only after discovery de-risks it.
A visual framework (Teresa Torres) for connecting desired outcomes to opportunities, solutions, and experiments.
Running the cheapest possible experiment to validate or invalidate a key assumption before building.
Teresa Torres's operationalisation of dual-track: weekly customer interviews, regular assumption tests, opportunity mapping.
How it works
PM + designer interview customers weekly, map opportunities, prototype solutions, run assumption tests. Output: validated backlog items ready for delivery.
Engineering builds pre-validated features in sprints. Product is available for discovery questions but not disrupting engineering daily.
Weekly PM + engineering sync to share discovery learnings, flag upcoming delivery items, and surface technical feasibility risks early.
Tools that support Dual-Track Agile
Industry standard for software development teams — most PMs will encounter Jira in their career
Exceptionally intuitive and visually clean interface — one of the lowest onboarding friction tools for non-technical teams
Highly visual and intuitive interface with color-coded boards — one of the easiest PM tools for non-technical teams to adopt
All-in-one platform replacing multiple tools — docs, whiteboards, goals, time tracking, chat, and project management in a single workspace
Unmatched flexibility as an all-in-one workspace — combines docs, wikis, databases, and project management in a single tool
Browser-based with no installation required — runs on any OS and enables instant sharing via URL, removing friction for cross-functional collaboration with PMs, engineers, and stakeholders
Best-in-class infinite canvas experience — the gold standard for collaborative whiteboarding with real-time multiplayer editing
De facto standard for workplace communication — most PMs will use Slack daily, and it appears constantly in job descriptions
Frequently Asked Questions
Typically 1–2 sprints. Far enough that engineering always has validated work to pull from; close enough that discovery learnings are still fresh when features are built.
In regular Scrum, discovery and delivery often happen in the same sprint — which means engineers wait while PMs figure out what to build. Dual-Track Agile explicitly separates these tracks so each can run at its natural pace.