Scrum for marketing teams: campaigns in Sprints

A marketing team works in short bursts: an email on Tuesday, a landing page on Thursday, a social campaign for a launch. Priorities shift with the market, requests arrive from sales, and the results of anything done are known only after it is out. This is not a stable, repeatable process, and it is a good fit for the empirical approach Scrum describes.

Why it fits

Marketing agility, as it is described in the research literature, means marketing decisions made in an agile manner using principles from the Agile Manifesto: opportunities or threats in the market are identified, decisions are made quickly with fast plausible delivery favoured over slower options, effects are monitored and further decisions follow iteratively. It is customer-focused and has shown benefits in volatile conditions.

The Scrum Guide's definition is about complex problems and not about software. It says Scrum is used in many domains with essentially complex work, and that the word Developers is used to simplify and not to exclude: if you get value from Scrum, consider yourself included. Writers, designers, analysts and channel managers are the Developers of a marketing team.

The team and the roles

A marketing Scrum Team might contain a copywriter, a designer, a data analyst, a channel specialist and a producer. The Product Owner is typically the head of marketing or a campaign lead, accountable for the value of the work and the order of the backlog. The Scrum Master, who can be one of the team, helps the team improve and removes impediments such as slow approvals.

The cross-functional requirement of the Guide means that the team holds all the skills to make and launch a piece of work. If every asset needs legal sign-off from outside that takes a week, the Sprint cannot finish. Agree a fast route in advance, such as pre-approved templates or a named reviewer with a one-day turnaround.

Backlog, Increment and Done

The backlog. A single ordered list of marketing work: campaigns, experiments, content, fixes to the website, reports. Items are written as outcomes, such as "a new parent can find our free trial from a search for tutors within two clicks", more than as tasks.

The Increment. A concrete step toward the Product Goal that is usable and meets the Definition of Done. For marketing, an Increment is something live that can be measured: a published landing page, a sent email sequence, a running ad test. A draft in a folder is not.

The Definition of Done. Typical lines: written and edited; on brand; legal review passed; tracking in place; published or scheduled; the result will be reported on a set date. The line about tracking matters most, because without it, the Sprint Review has nothing to inspect.

The Product Goal. A statement of the outcome for a period: "double the number of trial sign-ups from parents of primary school children by the end of the quarter." See outcomes vs output.

Sprint length and the events

Sprints of one or two weeks suit most marketing teams, because the market moves fast and results come within days. Longer campaigns are cut into parts.

Sprint Planning. Set a Sprint Goal about learning or reach: "learn which of two messages brings more qualified sign-ups." Select the items that serve it, and plan the tasks.

Daily Scrum. A short check on progress toward the goal and on the results coming in. Marketing teams often add a glance at live data.

Sprint Review. Show stakeholders what is live and what it did. This is the most useful change for marketing: the Review is about results as well as output. The Guide calls it a working session, so the discussion decides what to do next with the budget and the message.

Retrospective. Look at how the team worked: handoffs with design, approvals, tools.

Refinement. Prepare the next campaign items, including the questions they are meant to answer.

Handling fixed dates and requests

Campaigns often have dates that do not move, such as a product launch, a season or an event. Scrum handles this by fixing time and flexing scope: the team plans back from the date, orders the backlog so that the essentials come first and treats the rest as optional. See MoSCoW prioritisation.

Requests from sales, executives and partners arrive constantly. The Guide's rule applies: those wanting to change the backlog convince the Product Owner. A visible, ordered list gives the Product Owner a clear way to say where a request fits and what it displaces. See how a Product Owner says no. Many teams reserve a small share of capacity for urgent items, and make it explicit.

A worked example

This is an illustrative two-week Sprint for a team of five promoting a free trial.

Product Goal: raise trial sign-ups from primary-school parents by 40 percent this quarter.

Sprint Goal: find out which of two headlines brings more sign-ups from search traffic.

Backlog items selected: two versions of a landing page; a tracking set-up that separates the two; a small ad budget for each; a one-page report template.

Definition of Done: both pages live and tracked; the ad copy approved; a report scheduled for day ten.

On day three, sales ask for a case study for a prospect meeting. The Product Owner sees that it serves a different goal and asks whether it can wait; they agree that a short version will be drafted in the following Sprint. Midway, the analyst notices that one page loads slowly on phones, and the designer fixes it that day.

At the Sprint Review, the results appear: after eight days and 1,400 visits, version B converts at 6.1 percent against 4.4 for A. Stakeholders ask why. The copywriter points to the headline naming the child's year group. The Product Owner decides to adopt B for all search ads and to test a year-group variant next. The Retrospective notes that legal review took two days and agrees to create a pre-approved template.

The Sprint produced a decision and a better next experiment, and the team knew within two weeks.

Pitfalls

• Counting output only. Posts published are not results. See outcomes vs output.
• No tracking. Without measurement the Review is opinion.
• Too many campaigns at once. Limit work in progress to what the team can finish.
• Sprints that are just a calendar. A Sprint with no goal is a deadline.
• Approvals outside the Sprint. Plan for them or they will block it.
• Ignoring seasonality. Some results depend on the time of year. Compare like with like.
• Copying software terms. Story points and velocity are not required.

How to practise it

Write a Definition of Done for the marketing work you did last month and check that every item was measurable after release. In the simulator the Sponsor and stakeholders judge results, which mirrors a Review where outcomes and not drafts are discussed.