Dual-Track Agile for Discovery & Development
summary
Dual-track Agile runs discovery and development in parallel with continuous feedback and week-long, low-cost experiments (an experiment of the week cadence) feeding a development pipeline tracked on two boards. Teams of ~10–12 use a bridge role to prevent split teams, a prioritization matrix or value canvas to rank hypotheses, and acceptance criteria to move items to build, park, or kill. Result: faster, evidence-driven decisions, lower development cost, better stakeholder buy-in, and many investigated ideas never reach code.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:14Agenda
- 1:56Polls
- 4:36Theory
- 7:29Benefits
- 12:18Challenges
- 17:04Example
- 22:47Myths
- 29:06Team split
- 34:02DualTrack in small teams
- 36:01Team composition
- 37:40Red threat
- 38:28Prioritization
- 41:24Measurement
related talks
45mAgile Dual Track: How to Discover Product Without It Feeling Like Waterfall
52mShifting into continuous delivery
18mAgile leadership and technical mastery, a harmonious alliance
49mBaking Boards: Tweak the Recipe for Agile Development
25mAgile: The Bad Parts - Matt Parker, Martina Hodges-Schell
34mNative Agile Psychology of Teams and Individuals
47mAgile experience in changing environments and the challenges faced
48mTwo Dimensions Of Agile At Scale