agile --explain --no-brochure
What actually works, what fails, and why.
Most Agile content tells you what the frameworks say. This one tells you what happens when you use them — where the theory breaks down, and what experienced practitioners wish they’d known earlier.
done:
- code_reviewed: true
- tests_pass: true
- deployed_to_staging: true
- stakeholder_saw_it: pending
# "done" means usable, not "coded" Latest
all 32 posts →-
How to Eliminate Waste in Software Development: A Value Stream Mapping Guide
Find the waste in your software delivery with a value stream map: trace real work, measure wait and process time, name the waste and fix the biggest delay.
-
How to Implement DSDM: A Step-by-Step Guide
Implement DSDM on a real fixed-deadline project: staff the roles, run Feasibility and Foundations, build a MoSCoW list, plan timeboxes and protect the date.
-
How to Read a Burndown Chart: Patterns, Fixes and a Template
Set up a sprint burndown, capture the data daily, recognise the four common shapes, and act on what the chart shows before the sprint is lost.
-
The FDD Process: Feature-Driven Development's Five Processes, Step by Step
Run Feature-Driven Development's five processes on a real project: model, feature list, plan, design and build by feature, then track progress by milestone.
-
How to Write User Stories: Template and Examples
Write user stories that lead to the right software: a story template, Given/When/Then acceptance criteria, an INVEST checklist and five worked examples.
Topics
- ~/ foundations Where Agile came from, what it actually claims, and how it compares to the alternatives.
- ~/ frameworks Scrum, Kanban, XP, Lean, SAFe and the rest — what each one is for and where it breaks.
- ~/ roles The people who make or break an Agile team, and what each role is really responsible for.
- ~/ artifacts Backlogs, user stories, burndowns and the Definition of Done — used well and used badly.
house rules
No balanced-to-the-point-of-useless takes. No “it depends” without the specifics. Just direct guidance on the tools and practices that matter most.