Agile, explained properly.
AgilePowers is a working reference for Agile teams. Definitions that hold up under scrutiny, playbooks you can run this sprint, comparisons that admit the trade-offs, and research with the sample size printed on it.
Popular right now
Sprint retrospective Definition of Done Story points WIP limits Scrum vs Kanban Agile coachingSix ways in
Pick the door that matches what you need right now. They all link to each other anyway.
Agile Encyclopedia
Every term, role, ceremony and artifact, defined in plain language and linked to the practice it belongs to.
See all
Agile Playbooks
Step by step guides for the work itself. Planning, refinement, retros, splitting stories, restarting a stalled board.
See all
Agile Academy
Four tracks that take you from your first standup to running a transformation.
See all
Research
Adoption numbers, team benchmarks and survey data. Method and sample size shown every time.
See all
Comparisons
Agile or Scrum. Product Owner or Product Manager. Side by side, including where each one hurts.
See all
Templates
Ready made documents for the artifacts you write most often. Copy one, fill it in, and get on with the work.
See all
Agile in numbers
2001
12
95%
87%
The Agile Encyclopedia
Start with one term and follow it outward. Every entry says what it is, where it came from, how teams actually use it, and where it goes wrong.
Most popular
Playbooks you can run this week
Every playbook is written as a procedure. Who is in the room, how long it takes, what you bring, what you walk out with. Read one on Sunday, run it on Monday.
Learn Agile in order
Four tracks, built to be taken in sequence. Each one ends with something you can do on a real team, not a certificate you print out.
1
Beginner
Foundations. The Manifesto, the vocabulary, and what actually happens inside an iteration.
2
Practitioner
Run the ceremonies, write the stories, keep the board honest, and handle the stakeholder who still wants a Gantt chart.
3
Advanced
Flow metrics, dependency management, scaling patterns, and choosing a framework on purpose instead of by fashion.
4
Leadership
Funding, governance, operating models, and the culture work that decides whether any of it sticks.
Academy coming soon
Data instead of opinions
We run our own surveys and pull public datasets into one place. Sample size, method and raw counts get published with every study, so you can disagree with us properly.
Comparisons that admit the trade-offs
No framework wins every time. These break down where each one fits, what it costs to run, and the failure mode nobody puts on the conference slide.
Templates you can copy today
Each one is the version we actually use, not a blank grid with clever headings. Copy it into your tool, delete what does not apply, and get on with the work.
Agile User Story Template
The as a / I want / so that frame, with acceptance criteria written so they can actually be tested and a definition of ready that is not aspirational.
Agile Retrospective Meeting Template
A timed agenda for a sixty minute retro, prompts that get honest answers out of a quiet room, and somewhere to record actions with a name against them.
Agile Feature Template
One page per feature: the problem, who it affects, how it slices into stories that ship on their own, and what you will measure once it is out.
Who writes this
Every article is written by a practising Agile coach, scrum master or delivery lead, then read by a second practitioner before it goes up. Entries carry the author, the reviewer and the date they were last checked. When we get something wrong we fix it in place and publish what changed.
Latest from AgilePowers
Get better at Agile
Two emails a month. New research, new playbooks, and the occasional strong opinion about estimation. Unsubscribe in one click.
Read by 14,000 practitioners. We do not sell the list.