People and Patterns
summary
Argues that repeat problems are system patterns not people failures and gives concrete tools: draw a ripple diagram, map containers and differences, plot behavior-over-time graphs and build causal loop or current‑reality trees. Shows a prioritized‑backlog case with ~300 code packets where each developer knows ~6 items so work stalls, and a firm with six years of data showing zero projects within ±5% budget. Small batches, CI, daily customer involvement and moving one meeting day produce measurable improvement.
AI-written summary · about
chapters (5)
- 0:00Start
- 8:22Depicting the Flows of Communication
- 25:18Behavior over Time Graph
- 32:59Diagram of Effects
- 33:36Causal Loop Diagram
