Skip to content

5 min read

Agile for Campaigns

Summary

Agile for campaigns borrows the sprint-and-retrospective discipline from agile project management: short, time-boxed work cycles with a visible board, a fixed review at the end of each sprint, and a retrospective that drives continuous learning. It is the answer to campaigns that cannot plan a quarter ahead but can plan a week ahead. [source: wikipedia]

Body

Agile is a family of project-management methods that originated in software development and is now used across industries for work done under uncertainty. The defining characteristics are short, time-boxed iterations (sprints); a visible backlog of work; a regular sprint review; and a blameless retrospective that converts each sprint into an opportunity to learn and adapt [source: wikipedia]. Campaign teams face exactly that kind of uncertainty — political contexts shift, opponents move, windows open and close — so the same discipline applies: plan short, review often, adapt.

The core cycle:

  1. Sprint planning (30–60 min, weekly or bi-weekly) — the team selects what it can commit to completing in the sprint from the backlog, against the campaign’s current priorities.
  2. Daily stand-up (15 min) — each person says what they did yesterday, what they’re doing today, and any blocker. In small campaigns this can be async (a Slack message or a board comment).
  3. Sprint review (end of sprint) — demonstrate completed work to stakeholders or the wider team.
  4. Retrospective (end of sprint) — what went well, what did not, what changes the team will make next sprint. Keep it blameless and forward-looking. [source: people-power-manual]

Why campaigns benefit: The political cycle rarely respects a quarterly plan. A two-week sprint keeps the campaign responsive — the team can re-prioritise every two weeks rather than being locked into a plan written three months ago. The retrospective builds the learning habit that after-action review captures at the milestone level.

The Commons Library’s organising modules describe the sprint-and-retrospective discipline as part of the broader campaign planning rhythm that pairs with Kanban, OKRs and after-action reviews — agile is the rhythm, kanban is the visible flow, OKRs are the directional targets, and after-action review is the milestone-level learning [source: commons-library].

Constraints for volunteer campaigns: Daily stand-ups can feel like management overhead for unpaid contributors. Keep the sprint rhythm voluntary and the stand-up asynchronous. The sprint review should celebrate what the team achieved, not audit what it did not.

Where agile breaks down for campaigns: When the campaign has a hard external deadline (a vote, a court date, a protest permit expiry) — then the plan must be backwards-planned from that fixed date, not iterative. Agile is for the building phase; the escalation phase needs the Gantt chart.

Use it for

Rapid-response campaigns; digital campaigns where content and tactics shift weekly; managing a distributed coalition’s shared work without a central command; keeping a volunteer team aligned without formal management structures.

Worked examples

Open Questions

Does any campaigning-specific source document agile or sprint adaptation for advocacy organisations? The Commons Library Campaign Accelerator and the People Power Manual planning modules may have relevant adaptations. A case study of an agile campaign team would ground this page as primary.

FAQ

What is agile for campaigns?

Agile for campaigns is the borrowing of the sprint-and-retrospective discipline from agile project management: short, time-boxed work cycles with a visible board, a fixed review at the end of each sprint, and a retrospective that drives continuous learning. It is the answer to campaigns that cannot plan a quarter ahead but can plan a week ahead. [source: wikipedia]

What does the agile core cycle look like for a campaign?

The core cycle has four parts: sprint planning of thirty to sixty minutes weekly or bi-weekly, in which the team selects what it can commit to from the backlog; a daily stand-up of fifteen minutes in which each person reports what they did, what they will do, and any blocker; a sprint review at the end of the sprint to demonstrate completed work; and a retrospective, kept blameless and forward-looking. [source: people-power-manual]

How does agile fit with the broader campaign planning rhythm?

The Commons Library’s organising modules describe the sprint-and-retrospective discipline as part of the broader campaign planning rhythm that pairs with kanban, OKRs, and after-action reviews. Agile is the rhythm, kanban is the visible flow, OKRs are the directional targets, and after-action review is the milestone-level learning. [source: commons-library]

Where does agile break down for campaigns?

Agile breaks down when the campaign has a hard external deadline — a vote, a court date, a protest permit expiry. In that case the plan must be backwards-planned from the fixed date rather than iterative. Agile is for the building phase; the escalation phase needs a Gantt chart.

How should agile be adapted for volunteer campaigns?

For volunteer campaigns, daily stand-ups can feel like management overhead for unpaid contributors. The sprint rhythm should be kept voluntary and the stand-up asynchronous, for example a Slack message or a board comment. The sprint review should celebrate what the team achieved rather than audit what it did not.

Sources & verification

  • wikipedia — grounding: primary — Agile software development article (CC BY-SA 4.0)
  • people-power-manual — grounding: secondary — campaign-planning rhythm
  • commons-library — grounding: secondary — organising-modules framing

Last verified: 2026-07-09