Explain like I'm five · SW Eng

What is Agile/Scrum?

Agile and Scrum, told as a story about writing a book in short chapters instead of all at once, and showing each chapter to readers as it's done.

the writer spent two years on the whole book, showing readers only at the very endby the time it was done, readers' tastes had already changed

The writer spent two years on the whole book and showed readers only at the very end.By the time it was done, readers' tastes had already changed.

stick to the plan — no readers see it till the endhad I seen the draft earlier, I'd have told you soonershowing the book only at the end means the only chance to fix it comes at the end too

The plan shows readers nothing until the end, so their feedback only arrives once the book is done.Showing the book only at the end means the only chance to fix it comes at the end too.

ch.1 donech.2 donech.3 doneAgile/Scrum = writing the book in short chapters and showing each one to readersafter every chapter, reader feedback comes in and goes straight into the next one

Agile/Scrum means writing the book in short chapters and showing each one to readers.After every chapter, reader feedback comes in and goes straight into the next one.

Write in short cyclesone sprint = one chapter
Show it every timechecked with readers right away
Write top priority firstthe most important chapter goes first
Team looks back togetherfinding what to keep and change in the next chapter
SCRUM ROLES AND RHYTHMeditor (PO) — sets backlog prioritywriters (developers) — actually write the chaptersscrum master — clears blockers, helps work flowsprint — e.g. one chapter every two weeksthe editor owns priority, with the team's inputshort, repeated sprints reveal a wrong direction within weeks, not years

Scrum runs on roles and a short rhythm.The editor (PO) holds final accountability for priority, but adjusts it with the team's input each sprint.

short chapters bring reader feedback in soonerbut the writing itself is still up to the writerAgile is a way of working — it doesn't replace the writer's own skill

Reader feedback comes sooner, but the writer still has to write the chapters.Agile is a way of working — it doesn't replace the writer's own skill.

In one breath

Agile/Scrum = writing a book in short chapters, showing each one to readers, and revising as you go.

Agile is a philosophy for responding quickly to change in software development, and Scrum is its best-known framework. Work is split into sprints (usually 1-4 weeks), each ending with a review of the result and a retrospective on the process. A product owner sets priority, the developers execute, and a scrum master helps the process run smoothly.

When grown-ups say it

Agile
The philosophy of writing short and showing often. Responds quickly to change.
Scrum
The best-known framework for running Agile. Each sprint holds planning, daily check-ins, a review, and a retrospective.
Sprint
The short cycle for writing one chapter. Usually one to four weeks.
Product Backlog
The ranked list of chapters not yet written. The editor ranks it by priority.
Waterfall Model
Writing the whole book in one go, exactly to the original plan. The older style Agile pushes back against.
Requirements Engineering
Asking what readers want before writing. In Scrum, the contents and order of the backlog get questioned again every sprint. → the one who asks before writing
Daily Standup
A 15-minute check-in on progress, at the same time every day. Catches blockers quickly.
Retrospective
The team's look-back at the end of a chapter. Finds what to keep and change for the next sprint.
Next story
Looking Inside, or Just Reading the Outside →
Want another term as a picture book? Request →