What is an agile methodology?
An agile methodology is a way of managing work that assumes the plan will change. Instead of defining everything up front and delivering it at the end, the team works in short cycles, usually one to four weeks, called sprints or iterations. Each cycle produces something real that can be reviewed, and what the team learns from that review shapes the next cycle. The approach came out of software development in the early 2000s, where long projects kept delivering the wrong thing on time, and it has since spread to marketing, design and production.
The best known frameworks are Scrum, with its sprints, daily stand-ups, backlogs and retrospectives, and Kanban, which runs a continuous flow of work across a board with limits on how much is in progress at once. Most creative teams that call themselves agile use a loose mix of the two: a prioritized list of work, a short planning rhythm, a visible board and a habit of showing work early.
Why it matters
Why agile methodologies matter
Creative work rarely survives its first plan. The client sees the first cut and realizes what they actually wanted; the platform changes its format; the campaign that was supposed to run for a quarter needs a new version by Friday. A waterfall process, where every stage is signed off before the next begins, handles that badly, because change at the end costs the most. Agile handles it by making change the normal case: the work is always in a state that can be shown, judged and redirected.
It also builds trust. A client who sees progress every two weeks does not need to ask how it is going, and an agency that gets feedback every two weeks does not spend three months on the wrong idea. For always-on content, paid social and anything that is measured in days, agile is less a methodology than the only sensible way to work.
In practice
How agile methodologies work in practice
- 01
A team keeps a backlog, which is the ordered list of everything that could be made, with the most valuable items on top. At the start of each sprint it pulls what it can finish into a sprint plan. A short daily check-in keeps everyone on what they are doing and what is blocking them. At the end of the sprint the team shows the work, whether that is a set of ads, a cut of a film or a batch of designs, and the client or the stakeholders respond. A retrospective asks what to change about the process itself, and the next sprint begins with the backlog reordered.
- 02
For a creative agency the rhythm tends to map onto production. A paid social program runs in two-week sprints of make, launch, read the numbers, remake. A long film might run agile through development and post, where the cut is reviewed weekly, while the shoot itself is planned in detail because a crew on set cannot iterate. The producer plays the role the frameworks call a scrum master, protecting the team's time and keeping the board honest, and the creative director decides what is on top of the backlog.
At RIOT
Agile methodologies at RIOT
The Meta ad engine we ran for Homebase from February to April 2025 is agile by construction: a continuous cycle of making paid social creative, putting it on the platform, reading what the numbers said and producing the next round, on the platform's clock rather than a campaign calendar. The two months of social product films we made for Gantri ran the same way, as a series produced in cycles rather than a single delivery.
Watch out
What people get wrong about agile methodologies
Treating it as a ritual. Stand-ups, sprints and boards are tools; the point is to show work early and change course cheaply. Teams that hold every ceremony and still deliver one big reveal at the end are not agile, whatever the calendar says.
The other mistake is applying it where it does not fit. A shoot day cannot be iterated; a live event cannot be shipped in a minimum viable version. Agile suits work that can be made in pieces and judged in pieces. For the parts of production that cannot, a detailed plan is not a failure of agility, it is the job.
