This Is a Requirement. — "And what does it do?" — "It lights up blue!"
summary
Argues that poor requirements, not tools, are the main cause of mediocre projects (about 60%); user involvement is the top failure factor. Describes OXID’s concrete screening workflow: a numeric benefit rating combining effort, strategic fit, and target groups to produce a roadmap. Identifies three failure modes—emotional, communication, and decision‑development gaps—and recommends domain design with a Ubiquitous Language, pragmatic workshops, and realistic expectations about innovation success rates.
AI-written summary · about
chapters (7)
- 0:00Requirements engineering
- 7:35Emotional negotiations
- 12:10Communication gaps
- 18:08Dev versus decisions
- 24:19Innovation risks
- 30:58Summary
- 35:19Q&A
related talks
27mRequirements that you didn't know were there
14mGathering Requirements, and Rapidly Building Proof of Concepts
57mThings That Work So Well for Me I Can't Believe You're Not Using Them
27mYellow Brick Code: Lessons from The Wizard of Oz on Enhancing DevEx
47mHow To Build Future Proofed Applications
01h 00mRequirement Coverage: Myth or an Ultimate Goal
47mTangible Software Quality
36mHow Testers Can Help Paving the Future of Modern Requirements Engineering