Specification nightmare
summary
Fixed-price, three-year project with ~30 people (7 client, 22 dev) has sprawling, contradictory requirements—stories with 30–40 acceptance points and many estimated >100 hours—resulting in info obesity and missed value. Daily review highlights inconsistencies and missing attachments; a BA produces a flow diagram with story numbers; a critical chain visualizes dependencies and enables backlog reprioritization; PO training plus definition of done and definition of ready get adopted. Outcome: November go-live, steady sprint delivery, team fully occupied, finish moves three months earlier and losses shrink.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:37About my project
- 2:28Requirements
- 5:18Consequences
- 5:36Time was ticking
- 6:16Five steps
- 7:58Results
- 9:14Your role
- 10:00Understand the big picture
- 10:28Clear requirements
related talks
51mDependencies: Can your agile teams handle them? and if not.. how
37mApplying scaling techniques for product management
10mI am done -
46mScrum & Lean Startup in Action: Design to Delivery in 6 Months
01h 26mChaos Development: Removing Software as the Inhibitor of Agile
52mSmall Steps Are the Fastest Way Forward: Life Beyond Agile & Scrum
43mBacklogs – the good the bad and the ugly
34mFrom Waterfall To River – A Story Of Transitioning To Flow