Agility ≠ Speed
summary
Argues agility means the ability to change direction fast not raw throughput, so velocity has direction and story points often become time‑against‑time estimates. Treat the repository as codebase is a knowledge base: refactoring and tests are deliberate slowing that increases long‑term delivery. Uses OODA/PDCA loops, Amdahl‑style math and Conway’s law (and its reverse) to show adding people often creates diseconomies of scale — sometimes you must scale down not up to finish sooner and reduce risk.
AI-written summary · about
chapters (19)
- 0:00Intro
- 4:18agile, adjective
- 9:31Move fast an break things
- 10:22velocity
- 18:39utilisation
- 19:03quality of estimation
- 25:47The design process is an iterative one.
- 26:22You have to finish things - that's what you learn from, you learn by finishing things
- 29:52codified knowledge
- 32:06knowledge acquisition
- 34:02social negotiation
- 34:29model of participation
- 35:05The biggest advantage of autonomously working teams is risk reduction through increased group intelligence.
- 37:33People from diverse backgrounds might actually alter the behavior of a group's social majority in ways that lead to improved and more accurate group thinking.
- 40:28The four conditions that characterize wise crowds: diversity of opinion, independence, decentralization and aggregation
- 45:05Development has diseconomies of scale.
- 53:57It works, because the cycles of correction and recorrection, which occur during adaptation, are restricted to one subsystem at a time.
- 55:04The basic thesis ... is that organizations which design systems... are constrained to produce designs which are copies of the communication structures of these organizations.
- 55:56We have found a criterion for the structuring of design organizations a design effort should be organized according to the need for communication.
