Marketing Project Management
Marketing work doesn't fit neatly into either classic PM model
Project management methodologies were largely developed for software and construction, where a project has a defined start, a defined end, and a deliverable that either ships or doesn't. Marketing work is mostly the opposite: a continuous stream of overlapping campaigns, always-on channels that need daily attention, and urgent requests that arrive mid-sprint regardless of what was planned. Importing agile or waterfall wholesale, without adapting for that reality, is why so many marketing teams try a PM methodology, find it doesn't quite fit, and quietly abandon it within a quarter.
Agile vs. waterfall for marketing teams
Waterfall — sequential phases (plan, create, review, launch) completed fully before moving to the next — fits marketing work that genuinely has a long lead time and few surprises: a major product launch, a rebrand, an annual event. It gives stakeholders a clear, predictable timeline to plan around, but it handles mid-project change badly; a strategy shift discovered halfway through a waterfall plan usually means re-planning the whole remaining sequence.
Agile — short iterations (sprints) with a prioritized backlog reassessed regularly — fits the always-on parts of marketing much better: ongoing content production, paid campaign optimization, lifecycle email programs, anything where priorities legitimately shift week to week based on performance data. Its risk in a marketing context is that a backlog can become a dumping ground for every ad hoc request, and without discipline a 'sprint' stops meaning anything because the scope changes daily anyway.
Most functioning marketing teams run a hybrid: waterfall-style planning for big, date-locked initiatives (a major launch has a real deadline that can't move), wrapped inside an agile cadence for the team's ongoing work and the many smaller requests that interleave with it.
Agile vs. waterfall fit by marketing work type
| Work type | Better fit | Why |
|---|---|---|
| Major product launch / rebrand | Waterfall (with agile execution inside phases) | Hard external deadline, sequential dependencies (brand before creative before campaign) |
| Always-on content & social | Agile | Priorities shift with performance data week to week |
| Paid campaign optimization | Agile | Continuous, iterative, no fixed end state |
| Annual event planning | Waterfall | Long lead time, fixed date, heavy external dependencies |
| Lifecycle / CRM programs | Agile | Ongoing, backlog of improvements rather than a single deliverable |
The methodology matters less than having one visible backlog
Sprint planning for campaigns
Applying sprint planning to campaign work means breaking a campaign into the same granular tasks used in the campaign lifecycle (brief, build, QA, launch, report) and assigning realistic time estimates to each, then fitting that work into a fixed-length iteration (commonly one or two weeks) alongside everything else already committed. The failure mode specific to marketing sprint planning is treating a campaign as one undifferentiated task ('launch the spring campaign') rather than its component parts — that hides the fact that QA alone might eat two full days, and it's QA that gets silently dropped when the sprint runs long, which is exactly the mechanism behind most of the bugs described in campaign QA work.
Sprint retrospectives are worth keeping even in a marketing context specifically because campaign post-mortems tend to focus on results (did it convert) while retrospectives focus on process (did the brief arrive on time, was QA rushed, did the creative request get escalated late) — the two conversations answer different questions and both matter.
MARKETING SPRINT BOARD (2-week sprint, example)
BACKLOG (prioritized, visible to all stakeholders)
- Q2 webinar campaign (not yet scheduled)
- Homepage A/B test round 3
- Partner co-marketing asset request
THIS SPRINT
Campaign: Spring Promo Email Series
[ ] Brief finalized (0.5 day)
[ ] Copy + creative build (3 days)
[ ] QA pass (full checklist) (1 day) <-- do not compress
[ ] Launch + monitor (0.5 day)
[ ] Report back to brief (0.5 day)
Ongoing / always-on (capacity reserved, not a "task")
[ ] Social posting cadence
[ ] Inbound lead response SLA
[ ] Paid campaign daily optimization
CAPACITY CHECK: always-on work reserved BEFORE
new campaign work is committed to the sprint.Capacity planning against always-on demand
The hardest part of marketing project management is that a meaningful share of the team's time isn't allocatable to a project at all — it's ongoing operational demand: answering inbound lead response SLAs, daily paid campaign monitoring, routine content cadence, fielding ad hoc stakeholder requests. Teams that plan sprint capacity as if 100% of hours are available for new project work consistently overcommit, because the always-on work doesn't show up as a line item until it displaces something that was actually planned.
The fix is to reserve a realistic percentage of total capacity for always-on and ad hoc work before committing any of it to new project work — many teams find that 30-50% of marketing execution capacity is consumed by work that was never on a roadmap, and until that's made visible as a reserved allocation rather than an invisible tax, every sprint will look over-committed after the fact without anyone understanding why.
Ad hoc requests deserve a visible intake process, not a side door
What's next
Capacity planning inevitably raises the build-vs-outsource question — whether certain marketing execution work is better handled by an agency than by stretching an in-house team further.
Next: Agency vs In-House MarTech →
I build these systems professionally.
Whether it's a RAG pipeline, analytics migration, or AI workflow — let's talk.