Sneaking agility back into Agile
summary
Argues that traditional Agile workflows turn into a slow drift toward late-stage panic: teams run Sprints turning into feature cram, then delay, then bigger teams, then launch with no validation. Cites research-style figures—about 80–95% failure rate for new features—to justify adding quick discovery and staged validation. Shows concrete fixes called Trojan Horses: small process changes that embed rapid research, outcome metrics and gated experiments so launches test real demand before scaling.
AI-written summary · about
related talks
28mDual Track Agile
41mIntegrating User Experience and Agile
44mProduct Research as a Risk Mitigation Strategy for Product Development
46mThe final frontier - how to engage business users in agile.
41mLearning faster
36mMixing Lean UX & Agile Development
43mDesigning the Right Product
07mAdventures in Agile Research