Marketers are already in too many meetings; why should they keep up with some ridiculous Agile thing that just takes up space on their calendar?
Spinning up new Agile marketing teams comes with a host of challenges. We need to adapt existing frameworks to apply to our particular challenges, the existing team structure is rarely conducive to agility, and we almost never have a dedicated Scrum Master-like role.
The first two issues become obvious pretty quickly, and many teams take steps to address them before they begin work.
The final problem, however, tends to go unaddressed. In the midst of a flurry of change, who has time to hire or appoint someone to spend most of their time managing a process that’s supposed to create self-organizing teams?
There’s obviously a whole lot more we could unpack within this problem, but here I want to concentrate on the impact this lack of a dedicated Agile champion has on the all-important retrospective meeting.
Without someone who’s specifically tasked with leading retrospectives for a new Agile marketing team, they tend to go something like this:
Traditional manager: “So, how’s everybody feeling? What do you think about this last sprint?”
Agile marketing team members: nod heads “Ya...good.”
Traditional manager: “Ok great. See you all at sprint planning.”
It’s even worse if teams are distributed, because you might not even be able to see your teammates’ head nods. Marketers are already in too many meetings; why should they keep up with some ridiculous Agile thing that just takes up space on their calendar?
As you can imagine, this kind of meeting quickly gets dropped.
Of course, dropping the retrospective or allowing it to limp along in this sad state is a sure fire recipe for failure. Even if you can’t hire a full time Agile Lead or Scrum Master, there are ways to maintain rigor around your retro.
Whatever framework we use, and whatever team structure we implement, Agile marketers are always working through the process of translation. The original Agile practices don’t always work for us, so we’ve got to be ready to evolve them.
Without an effective, rigorous retrospective meeting, this continuous evolution simply can’t happen.
Even if there’s no budget (or time, or space, or whatever) to bring on a full-time Scrum Master or coach, find ways to make your retrospectives rigorous. Perhaps more than any other, this meeting can determine whether Agile marketing flies or fails.
Here’s a secret you didn’t know: Developers hate your retros. Not all developers and hopefully not all of your retros, but at some point, a developer has sat in one of your meetings and thought “this retro sucks”. You might wonder if this is a problem, but at the heart of agile lies one key concept, continuous improvement.
In order to keep your team retrospectives productive in the long-term, there are a couple of proven tactics you can use as a facilitator (but also as a team member). To make sure your team is excited for this meeting and you’re leading the team down the path of actionable takeaways, keep these following best practices at bay when you are planning or hosting your upcoming retrospectives.