Review Requirements
summary
Sketch note maps requirements into action and shows concrete habits: use Cornell notes or mind maps for recall, carry planning-poker question cards of who what when where why how, practice exploratory testing with physical black boxes and tiny bug props, and draw a shared one-week integration diagram that was built in seven days and immediately reduced misinterpretation. Also assess testability via controllability automaticity observability separation understandability and heterogeneity and treat requirements as recipes not detailed specs.
AI-written summary · about
chapters (12)
- 0:00Start
- 7:03Lateral Inference
- 10:26What Do You Do When You Enter an Elevator
- 15:24How To Take Notes
- 17:49Types of Thinking
- 20:12Critical Thinking Questions
- 20:50Planning Poker
- 21:44How Do You Eat an Elephant
- 25:25Is There Such a Thing as Automated Testing
- 28:19The Difference between Risks and Open Issues
- 29:31Peter Principle
- 31:27Why Should Your Employer Pay You To Learn
related talks
26mIdeation and Prototyping: Think Bigger, Fail Quicker
35mA Developer's guide to the Design Process
55mFrom Squiggles to Straight Lines: Sketch To Make Decisions & Get On With It
47mQualityStorming: Collaborative Modelling for Quality Requirements
41mMapping Experiences: From Insight To Action
27mDeeper Understanding & Better Communication through Art
28mCreative Test Reporting Integrating Pixar Storytelling Ideas into SW Quality Assurance
49mPragmatic Sketching