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:

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