Agile: when the team drives direction

Agile project management is more fluid. Short-term deadlines, the team drives the direction, and the plan changes as the work teaches you what the work actually is.

Agile is built around the team and the member. Cycles are short — usually two weeks — and the deliverable at the end of each cycle is a working thing that the people who will use it can react to. The next cycle adjusts based on what you learned. The plan is not the document; the plan is the practice.

The pros: flexibility, member or client involvement throughout, and a steady drumbeat of feedback that catches mistakes early. The cons: deliverables are not gated by phase, so in larger teams (especially cross-departmental ones) it can be harder to keep everyone on the same page. Miscommunication happens. Two people quietly building the same thing is common. The professional certification associated with agile is the Scrum Alliance Certified ScrumMaster.

Agile fits community work where the right answer is not known yet. A new program. A membership tier launch. A pilot. The 1:1 conversation rounds where you really do not know what you will learn until you start having them.

A real agile cycle in community work looks like: pick a two-week chunk, talk to ten members, ship one small thing, look at what happened, decide what to do for the next two weeks. The discipline is the cycle, not the framework. Do not let anyone sell you a sprint planning ceremony you do not need.