Dual-Track Agile: How Discovery Changes What You Estimate
In a dual-track agile setup, one track is continuously discovering and validating what to build while the other track is building it. This affects estimation in ways most teams don't fully account for.
What runs in each track
Discovery track: user research, prototype testing, solution validation. Output: validated problem/solution pairs that are ready to be built.
Delivery track: sprint planning, development, testing, release. Input: stories from the discovery track.
The estimation implication
Stories that come from discovery have already been validated - the team knows users want the feature and has tested a basic version of the approach. This reduces scope uncertainty significantly and makes estimates more reliable.
Stories that enter delivery directly from a backlog or stakeholder request - without discovery - have higher uncertainty. Your estimates should reflect that.
How to signal uncertainty in your estimates
Some teams use a confidence tag alongside the estimate: 5 (high confidence) vs 5 (low confidence). This tells the Product Owner that two 5-point stories are not equally plannable - one has been de-risked through discovery, the other hasn't.
When discovery and delivery get out of sync
If discovery gets too far ahead, the delivery team receives a backlog of validated ideas but loses the context from the research. Estimates suffer because developers are estimating based on specs rather than shared understanding.
If delivery catches up to discovery, you get a "discovery gap" where the team has no validated work to pull from. This is when pressure mounts to skip discovery and estimate unvalidated ideas - which increases delivery risk.
Keeping the tracks aligned
Aim for discovery to run roughly one sprint ahead of delivery. This gives the delivery team enough lead time to ask questions and raise concerns while the research is still fresh.
Discovery doesn't eliminate estimation uncertainty - it moves it earlier in the process, where it's cheaper to resolve.