Skip to main content

Dual-track Product Development

One of the trickiest questions product people ask themselves is: how can I innovate on my product while being in a constant delivery mode?

Innovate while delivering

Every product person gets to that question sooner or later. Usually, it happens with more or less mature products in big companies. Where a large group of stakeholders fights for pushing their requirements in. Roadmaps have been created for years ahead and technical debt keeps on growing. At that time product backlog is usually consists of hundreds of stories, some of which created a couple of years ago. Product owner of such backlog has her "hat on fire"(which we always have), running around stakeholders to reach some kind of consensus and sense of priority. She already forgot about all those great features she wanted to try out. There is no time to innovate when you run from one fire to another.

Is there a better way? How come some companies are able to innovate while continuously delivering their products?

Dual-track product development

There is a better way and it's called Dual-track product development.
You can find it also by the following names:

  • Dual-track agile
  • Dual-track scrum

SVPG popularized that concept in product management community a while ago.
It describes a way to combine two vital processes in product development: product discovery and product delivery.
By following dual-track product development company could discover a product that is valuable, usable and feasible. Then it could deliver it effectively.
All with one team.

A word about teams

The concept of cross-functional product teams should not be alien to anyone. Cross-functional product team consists of members with the different expertise needed to deliver the right product effectively to a market. The key to a cross-functional team is rather simple: it should be able to perform the entire circle of product development. From an idea to a post-release support. Such team should be responsible for a product fully and not be dependent on anybody else in their work.


The biggest challenge for the cross-functional team is: how to combine product discovery and product delivery?
Most teams I've seen been optimized for delivery. Partly because those teams originated from an IT department and tech always tend to optimize for delivery. When the product gets involved with an ambitious challenge to increase a value of a product - a set of problems appears.
  • Requirements get blurrier
  • Velocity drops
  • Technical debt increases
  • Happiness takes a hit
To overcome those challenges team needs a formal dual-track development process.

Two backlogs

To effectively do dual-track PD split your backlog in two: discovery backlog and delivery backlog. Discovery backlog should consist of ideas and concepts for further validation. While delivery backlog should include only the items ready to be coded and released.
Tip to try out: keep a story in a discovery backlog until it's fully defined, including UX, design, and copy. So then when a story gets to a delivery backlog developers could start implementation right away.

Discovery track
In this track, you need to prioritize, validate and decide upon product ideas.

Delivery track
Here is your usual development process with user stories, sprints, reviews, and releases.

Working together

Both product discovery and delivery could be and should be performed by the same team. You not necessary need the entire team to do product discovery ( a minimal set is: developer, UX, nd PO) but it's always better to keep everybody in the loop. It builds the shared understanding of user problems, market and business you're in.


You can either combine discovery and delivery within one sprint or split them in the independent sprints.
Combining gives the following advantages:

  • Clarity on what everyone is doing
  • Shared artefacts (standups, meetings)
  • Better information exchange

Splitting discovery and delivery sprints gives the following advantages:

  • Better focus on each track
  • Some time savings
  • Independent discovery and delivery velocities
  • Sprint lengths could be different


No matter what way with your sprints you'd choose it's a good practice to have the entire team and key stakeholders on the review meeting(s) for discovery and delivery sprints. It is vital to present the findings of a discovery work and therefore prepare the team and the stakeholders on what will come in the future.
Ideas from the discovery backlog that been validated should be moved to a delivery backlog.

Wrapping it up

There is a way for product teams to effectively combine product discovery and product delivery. Dual-track product development concept could be easily adjusted to your company situation and team setup. By following dual-track PD cross-functional product team could reach peak performance in creating valuable products.

Learn More

Popular posts from this blog

Product management and operations tools - Jira Product Discovery review

  JPD is a new player in the market of product management software. Jira (and the whole Atlassian suite) has been one of the most popular tool stacks for teams to deliver software products. Now they're adding a missing piece - product discovery.

Product Vision: an elevator pitch for your product

On this blog, I write a lot about making data-driven decisions . But what if you just starting to think about your product? You have a vague idea and nothing more. No point to go for prototyping or even talking to customers as you don't know yet who to talk to and what to talk about. In such situation - start from creating a product vision.

2 simple but powerful filters for your problem and product ideas

Nowadays lots of people and companies want to innovate. They want to generate new ideas and turn them into profitable products. But how would you separate good ideas from not so good ones? How would you make sure you invest only in good ideas?