Agile for Mere Mortals
Agile is a way of building software in small steps, checking what you built, and adjusting — instead of planning everything up front and hoping. This guide covers the manifesto behind it, Scrum and Kanban (the two big frameworks), user stories, estimation, how agile goes wrong in the real world, and what parts are worth keeping when it's just you or a tiny team.
No certifications required. Ideas first, then the practices that actually earn their keep.
What this guide covers
- What agile is — the manifesto, the four values, and what agile is not
- Scrum — sprints, roles, and ceremonies: the most common framework, explained straight
- Kanban — visualizing flow and limiting work in progress: the quieter alternative
- User stories — writing work items people can actually build from
- Planning and estimation — story points, velocity, and why estimates are always wrong
- How agile goes wrong — cargo-cult agile, micromanagement theater, and other failure modes
- Agile for small teams — what to keep when it's just you or three people
- Troubleshooting — symptom → fix, seven ways
What it doesn't cover
Scaling frameworks (SAFe, LeSS), agile coaching as a career, and the certification industry. This guide is about doing agile on a real team — not selling it.
How to use this guide
Agile is methodology, not tooling, so there are no commands to run here. Claims about Scrum and Kanban were checked against the Scrum Guide and standard Kanban references before shipping. Framework details drift over the years; anything version-sensitive says so.