The Two Tracks

Discovery and delivery run in parallel, not in sequence. Discovery feeds delivery. Delivery surfaces insights that feed discovery.

Discovery Track
Delivery Track
Convergence Point
Discovery Track
PM, Design, Stakeholders
Delivery Track
Devs, PM, Scrum Master
Step 1
Problems & Opportunities
Identify user needs, stakeholder feedback, and market signals
▼
Step 1
Sprint Backlog
Committed stories from planning, estimated and ready for development
▼
Step 2
Stakeholder Research
Interviews, data analysis, co-creation sessions, and field observations
▼
Step 2
Development
Build features, write tests, submit pull requests
▼
Step 3
Problem Framing
Define the problem clearly, identify constraints and success criteria
▼
Step 3
Code Review & QA
Peer review, automated testing, manual QA validation
▼
Step 4
Solution Exploration
Generate options, evaluate trade-offs, assess feasibility with engineers
▼
Step 4
Deployment
Deploy continuously as code is ready and approved
▼
Step 5
Prototyping & Validation
Test solutions with real users before committing to full builds
▼
Step 5
Release
Stakeholder communication, release notes, user-facing rollout
Convergence
Backlog Grooming — Thursday, Week 2
Validated discoveries become dev-ready stories. PM presents opportunities, engineers t-shirt size, team commits to what's next.
↻
The tracks form a continuous cycle. Discovery feeds delivery with validated backlog items. Delivery surfaces real-world insights — usage patterns, technical constraints, edge cases — that feed back into discovery. They run in parallel, not in sequence.