Want to Engage Managers in Agile? Stop Using Agile Jargon
If you want to engage managers and executives in Agile, avoid agile jargon from existing agile frameworks and models such as: sprint (Scrum), servant-leader, release train (SAFe), or made-up words such as anticipaction (Agile Profile).
Not only do managers and executives not have common understanding of agile terminology, but more importantly they do not necessarily have interest for "becoming agile" in the first place. At first this might seem like an intractable obstacle but it's actually quite refreshing. Indeed it helps talking in terms of real business and management challenges instead of focusing on agile concepts and methodology. And guess what? Agile values and practices can be expressed quite well in common management language.
"Agile values and practices can be expressed quite well in common management language."
Actually, the broader and higher my interventions for agile transformation, the less I talk about agile.
In my opinion, promoters of agile methods, tools and frameworks have packaged agile commercially, creating a layer of opacity that backfires when we address management and organizational agility.
"The higher my level of intervention for agile transformation, the less I talk about agile".
Agile jargon originated from two broad sources that have shaped the general (mis)understanding of agile today. First the software development grassroots becoming popular more than a decade ago with frameworks such as Scrum and Extreme Programming (XP), now going more enterprise-level with SAFe and many other siblings. And second, strategy management firms and business schools such as Gartner and Harvard, as well as leading management authors such as Steve Denning (Radical Management) and Jurgen Appelo (Management 3.0) who joined the trend a few years ago and developed their own agile terminology.
Let's have a look at a list of agile wordings that have created confusion in many, many discussions (I've been there…) and find an equivalent in common management language.
VUCA = volatile (leave UCA for long-form explanation)
Bimodal = organized both for efficiency and innovation (or for predictability and exploration)
Velocity = speed of value delivery
User story, epic = product feature
Sprint = x-week iteration (where x is a number)
MVP, minimum viable product = first partial solution
Increment, release = new features delivered to users
Product owner = client representative
Scrum Master = team facilitator
Synchronize = fast decision-making across hierarchy and functions
Servant-leader = coach-style manager
Product backlog = prioritized list of features
Whole team, squad = end-to-end team
Budget-boxed = fixed budget
Time-boxed = fixed delivery date
Variable scope = dynamic prioritized list of features
Delivered value = must refer to context-specific metrics (that's a tricky one - unexplained, many see it as ROI which it's not)
Purists will find that these are not entirely equivalent. I can live with that. The goal is to get a message through, not to write a glossary.
Share your experience!
ABOUT THE AUTHOR:
Bruno Collet helps organizations benefit from agility, mainly in the area of digital transformation. He develops the Metamorphose framework to accelerate transformation results. His career has led him to collaborate with organizations in Montreal, Belgium and elsewhere, including the Société de Transport de Montréal (STM), National Bank of Canada, Loto-Québec and Proximus (formerly Belgacom). Holder of MBA, MScIT, PMP and PMI-ACP degrees, Bruno Collet is also author of a blog on agile transformation, and speaker at PMI, Agile Tour Montréal and Agile China.
Disclaimer: trademarks used in this article are used for illustrative purpose only. The article is not sponsored by, or associated with, the trademark owners.