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:

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