People, Process, & Patterns
summary
Claim: projects fail mostly because of people not tech. Specifics: active listening techniques—mirroring, labeling, paraphrasing—and slow measured tone reduce conflict; quick experiment yields a social 50/50 norm. Process: a dual‑track discovery and delivery model with discovery backlog, validation cycles, Kanban feeding a delivery Scrum backlog. Tools and artifacts: paper prototypes, InVision, Principle, React component libraries and automated pattern libraries. Measurable result: validate early to avoid rework—aim for ~78% task success; a client hit mid‑50s/low‑60s after two years of waterfall.
AI-written summary · about
chapters (6)
- 0:00Start
- 23:22TRADITIONAL AGILE PROCESS
- 26:26LIFECYCLE OF A REQUIREMENT
- 31:33DUAL TRACK DISCOVERY / DELIVERY
- 36:10WHAT IS A PATTERN LIBRARY?
- 39:07WHY ARE PATTERN LIBRARIES USEFUL?
related talks
01h 02mPeople and Patterns
33mEffective Agile Processes: It’s All About People
24mWhatever Works – Scrum, Kanban, or Nothing?
46mIt’s Never a Technology Problem: Using Experience to Solve the Problem
20mWorking with Others and Delivering as a Team — Bridges Seen Through Human Relationships
05mContext-Driven Practices
48mBuilding a Product and Engineering Relationship that Works
42mHow Doing the Little Things Well Makes the Big Things Possible