Search
Close this search box.
Search
Close this search box.
Search
Close this search box.

Do you NEED to Scale Agile Marketing? (Scaled Agile Marketing Series – Part 3)

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

In earlier posts in our Scaled Agile Marketing, we looked at whether you even need Agile Marketing and then what typically triggers a serious discussion about Agile Marketing. In this post, we move to the next step – figuring out if you need Scaled Agile Marketing.

So – Do you need Scaled Agile Marketing? 

Scaling isn’t just a function of the number of people in the marketing organization. It’s more a function of how many marketers need to work together as part of one customer journey/experience.

Let’s look at an example. In the diagram below you can see a typical marketing organization that would possibly have a need for some scaling approach. They have agile teams that cross-cut the different marketing functions – focusing on delivering marketing value/impact for a specific product/customer journey rather than focusing on a specific marketing function/task.

Map it to your organization. If your teams are truly autonomous and work on separate backlogs and activities with minimal dependency then you might not need a full-fledged scaling approach.

If on the other hand, they ARE working on one bigger customer journey, have some dependencies across teams and some floating specialists that need to be involved in multiple teams or are considering synergies and adjacency campaigns (e.g. If you’re using an agile ALM tool you can probably benefit from our Continuous Integration or Portfolio-level tools), a scaling approach would benefit you.

In this context, SAFe’s Agile Marketing Train (A name coined in the field for the Agile Release Train in the context of Marketing) with its Program Increment Planning, Single Program Backlog, and System Demos provide useful guidance.

Working with Agencies

In many cases, marketing organizations work with external marketing/advertising agencies to deliver some of their campaigns or some of the materials for their campaigns. In most cases, the way these relationships work doesn’t map well to “everybody working on one agile team” and some sort of scaling solution is required.

A rising trend is the “Internal Agency” model (see https://hbr.org/2015/07/6-reasons-marketing-is-moving-in-house) in which an internal agency is created as a shared service that supports the various lines of business in the organization. While getting rid of the dependency on an external vendor, this “shared service” presents its own scaling challenges.

SAFe provides a couple of options for how to deal with internal/external “suppliers” – for example, they can become separate “supplier” Agile Marketing Train on a bigger Solution Train or a “supplier” team that is a “component”/”specialized” team inside an Agile Marketing Train. In any case, SAFe provides guidance for how to involve them in a planning and execution cadence and how to create realistic plans considering their capabilities and availability without forcing them to be members of agile teams (although that is certainly an option and will be recommended in some cases).

Longer-term activities such as events, strategic campaigns

Most agile marketing organizations run a mix of high-tempo testing that is a great fit for agile iterations/flow with frequent planning but also some longer-horizon activities such as conferences, webinars, and big product launches, that require more predictability and visibility beyond the “next 2 weeks” that classic team-level agile provides.

SAFe’s combination of high-tempo team-level agility with the Program level with its Program Increment Planning, Roadmap, and visibility to Features helps deal with this mix of demands from the marketing organization.

There’s a preference for SAFe in the enterprise

In many organizations Marketing is following the product development/management organization into Agile. If a product development/management organization chose SAFe as its agile approach, you will benefit from using it as your approach as well.

The same framework means using the same language. Even after adjusting SAFe to a marketing vernacular, it is still SAFe and marketers will be able to understand developers and vice versa.

The same framework means the ability to share expertise, knowledge, and training. While Agile Marketing isn’t exactly Agile Development a good agile coach or SAFe Program Consultant (SPC) can learn the marketing nuances over time.

Using the same framework means you’re better prepared for the day you will actually bring product development and marketing into the same customer experience value stream. While the typical starting point is for marketing to create “Agile Marketing Trains” focused on the marketing/customer journey value stream, many organizations are executing a “Digital Transformation” which means an emphasis on the digital experience that combines both marketing/sales and usage touchpoints. (See Oracle’s Customer Experience Lifecycle for an example)

With this one bigger customer life-cycle in mind, more and more organizations have a vision of creating “Agile Customer Experience (CX) Trains” combining development, marketing, sales, and others. These trains are needed in order to iterate and learn at the speed needed to compete in the digital age. Starting from the same or similar framework will ease the transition to these sorts of trains – reducing the babel tower effect that might happen otherwise.

If you see a need for agile marketing AND your context fits at least some of these descriptions/environments, you probably need some scaled agile marketing patterns, which will be the topic of our next blog in the series.

Subscribe for Email Updates:

Categories:

Tags:

Test Driven Development
chatgpt
Slides
Perfection Game
Agile Israel
Jira Plans
Webinar
Games and Exercises
SAFe
ALM Tools
Agile Product Development
RSA
Presentation
ROI
Elastic Leadership
Software Development
TDD
Agile Exercises
Implementing SAFe
Entrepreneurial Operating System®
Certification
IT Operations
LPM
Lean-Agile Software Development
Nexus vs SAFe
Risk-aware Product Development
Scrum Primer
Kanban Game
Agile Release Management
Frameworks
Product Ownership
AI
LeSS
Scrum Values
Professional Scrum Product Owner
Managing Projects
Hybrid Work
Operational Value Stream
Enterprise DevOps
ATDD vs. BDD
RTE
LAB
Achieve Business Agility
DevOps
agileisrael
Lean Risk Management
Kanban
Agile Development
Lean and Agile Principles and Practices
Reading List
NIT
EOS®
Value Streams
Acceptance Test-Driven Development
Scrum Master
Principles of Lean-Agile Leadership
Atlaassian
Continuous Deployment
ScrumMaster Tales
Implementation of Lean and Agile
Introduction to ATDD
Continuous Improvement
Atlassian
Agile
Rapid RTC
System Archetypes
Limiting Work in Progress
Agile Testing Practices
Sprint Planning
Program Increment
The Kanban Method
predictability
Jira
GanttBan
Artificial Intelligence
PI Planning
Applying Agile Methodology
Spotify
Lean Agile Management
speed @ scale
Kanban 101
Risk Management in Kanban
Nexus
Built-In Quality
Agile Release Planning
Amdocs
Agile Marketing
Tools
Agile Program
Scaled Agile Framework
ARTs
Nexus and SAFe
Agile Project
Coaching Agile Teams
RTE Role
Agile Delivery
Lean Agile Basics
Agile Games
Risk Management on Agile Projects
An Appreciative Retrospective
A Kanban System for Software Engineering
Kanban Basics
Scrum and XP
Manage Budget Creation
BDD
Portfolio for Jira
POPM
Managing Risk on Agile Projects
Quality Assurance
Iterative Incremental Development
Lean Software Development
Continuous Delivery
Agility
Lean Agile Organization
Agile and DevOps Journey
Nexus Integration Team
Continuous Planning
System Integration Environments
Systems Thinking
Agile Outsourcing
lean agile change management
Pomodoro Technique
Engineering Practices
Professional Scrum Master
The Agile Coach
Agile Community
QA
Keith Sawyer
Agile Games and Exercises
Sprint Retrospectives
WIP
AI Artificial Intelligence
Lean and Agile Techniques
Development Value Streams
ART Success
Professional Scrum with Kanban
Scrum
Certified SAFe
ATDD
Large Scale Scrum
Agile Basics
Agile in the Enterprise
Release Train Engineer
Agile for Embedded Systems
Daily Scrum
SAFe DevOps
Sprint Iteration
Code
Legacy Enterprise
Agile Mindset
Legacy Code
Agile India
Covid19
User stories
Agile Contracts Best Practices
Product Management
Lean-Agile Budgeting
Introduction to Test Driven Development
Agile Project Management
System Team
Jira Cloud
Continuous Integration
Lean Startup
Agile Product Ownership
Lean Budgeting
AgileSparks
Lean Agile Leadership
Accelerate Value Delivery At Scale
Releases Using Lean
Planning
Scrum Master Role
Kaizen
PI Objectives
Self-organization
Scrum.org
Kanban Kickstart Example
Agile Assembly Architecture
Team Flow
speed at scale
SAFe Release Planning
Software Development Estimation
Story Slicing
Scrum With Kanban
SA
Agile Risk Management
Nexus and Kanban
Jira admin
Change Management
Advanced Roadmaps
Process Improvement
Lean Agile
Agile Techniques
Tips
Kaizen Workshop
Agile Israel Events
Effective Agile Retrospectives
Video
SPC
What Is Kanban
Scrum Guide
AgileSparks
Logo
Enable registration in settings - general

Contact Us

Request for additional information and prices

AgileSparks Newsletter

Subscribe to our newsletter, and stay updated on the latest Agile news and events

This website uses Cookies to provide a better experience
Shopping cart