3 reasons why agile design fails
summary
Claims three concrete failure modes: high uncertainty, scrum rules versus design reality, and interdisciplinary dependencies, with the fix being concrete changes not platitudes. Teams adopt one-week design sprints, double reviews (internal dev feasibility + weekly client review), track overall design budget percentage instead of ticket count, and accept guesstimates for exploratory work. Tooling includes a Figma–Jira sync plugin (jro ticket sync) and Figma Developer Mode; the plugin noticeably improves handoff and reduces rework.
AI-written summary · about
chapters (7)
- 0:00Agile design challenges
- 4:27Agile design integration struggles
- 7:15Early design uncertainty
- 13:32Scrum vs design reality
- 19:34Design dependencies
- 25:35Flawless design handoff
- 32:36Q&A
related talks
40mAgile is Broken & It’s the Product Manager’s Fault
02mDesign after Agile: How to Succeed by Trying Less
18mCollaboration in product design
40mRegain Benefits from Agile Software Development
45mGreat UX, Despite Agile: How to Get the Best Out of Your Design Team in Agile Projects
47mBuild Agility with Design Sprints
22m7 steps to destroy an Agile Transformation
25mAgile: The Bad Parts - Matt Parker, Martina Hodges-Schell