Douglas Squirrel - We've been doing requirements wrong all along, here's what to do instead!
Playback access may have expired or the stream is unavailable. Reload the page to request fresh access.
Another tab is open for this lesson. You can keep watching here; the newest position wins.
Saved position may be approximate: the browser clock disagreed with the server.
Your free preview has ended
Create a free account to finish this lesson, or subscribe for the full library.
Your viewing record
No viewing recorded yet. Press play; your position is saved about every 10 seconds.
Last viewed . Last position —.
Completion
Based on 0:00 of unique watched video. Repeats and skipped parts do not increase it.
Are you stuck with traditional "requirements"? Squirrel, with 40+ years in coding, reveals why we should think in "requests" instead. Drawing from "The Big Book of Concepts," he explores the futility of control in understanding user needs. Discover his innovative approach for tech productivity, and how his 1450 cottage in Frogholt, England influences his thinking!
Recommended Resources
- Cynefin, The framework that explains the difference between Ordered, Complicated, Complex and Chaotic domains
- The Big Book of concepts, by Gregory Murphy****
- The Squirrel Squadron Community****
- Specification by example, by Gojko Adzic
Parting Word of Advice
"Stop using the word requirements. Use a different word."
About Douglas Squirrel Squirrel has been coding for more than forty years and has led software teams for twenty. He uses the power of conversations to create dramatic productivity gains in technology organisations of all sizes. Squirrel’s experience includes growing software teams as a CTO in startups from fintech to biotech to music, and everything in between. He lives in Frogholt, England, in a timber-framed cottage built in the year 1450. You can link with Douglas Squirrel on LinkedIn.
Comments (0)
Log in to join the discussion.
No comments yet. Be the first to comment.