Agile, Scrum & Flow
What the guides actually say, what the evidence actually shows - and how to tell a team working from one performing.
- 1Four values and a "while"The Agile Manifesto is 68 words long, and the most-ignored part is the last sentence. Read the whole thing, find the line that rules out "no documentation" and "no plan", and meet the principles the rest of this trail tests.Runs in your browser12 min+30 XP
- 2Scrum as written, not as rumouredMost of what people "know" about Scrum isn't in the Scrum Guide - and some of it was taken out in 2020. Read the framework as its authors wrote it, correct five myths against the texts, and work out what each event is actually for.Runs in your browser18 min+45 XP
- 3Count the work, then limit itStarting more work feels like progress. Measure what it actually does - work in progress, cycle time, throughput - check the books with Little's Law, and find out why a WIP limit helps until the day it starves the team.Runs in your browser20 min+50 XP
- 4Forecasts, not promisesVelocity becomes a target, the points go up, and delivery doesn't move. See what the Scrum Guide actually says about estimates, watch a velocity target inflate the numbers, and find the one count that can't be gamed.Runs in your browser16 min+40 XP
- 5The engineering Scrum leaves outScrum is deliberately silent on how to build the software. Extreme Programming isn't. Watch a weak Definition of Done make the "finished" count lie, and see why the practices that keep software working are what the ceremonies were for.Runs in your browser16 min+40 XP
- 6What the evidence says about teamsEvery framework promises better teams. What has actually been measured? Read Google's Project Aristotle, DORA's culture findings and a 2,638-effect-size meta-analysis the careful way - as associations, not recipes - and test a practitioner's hypothesis against them.Runs in your browser18 min+40 XP
- 7Frameworks for many teamsSAFe, LeSS, Scrum@Scale and the "Spotify model" each promise a way to run many teams. Read each in its own words, read its critics in theirs, and learn why copying another company's snapshot is the most common way to get it wrong.Runs in your browser16 min+40 XP
- 8Agile in name only: how you'd knowThe stand-ups happen, the board is busy, the sprints end on time - and nothing tested reaches users. Learn the one test agile's own founders keep coming back to, apply it to four teams, and read two government projects without the usual myths.Runs in your browser18 min+45 XP