The Agile Political Landscape Series: LeSS and The Greens

Please note: This is the third article in a series that explores mapping agile certifications to what Daniel Luschwitz and I have coined the Agile Political Spectrum. The previous blogs in the series are available here:

What if Agile Certifications were a Political Party?
The Agile Political Landscape Series: PRINCE2 Agile and One Nation

A note on our political comparisons: These political comparisons are playful metaphors designed to illustrate philosophical positions on the agile spectrum. No certification body was harmed in the making of this analysis.

Every political spectrum needs its idealists – parties that refuse to compromise on their principles that would make the world a better place. In the agile certification world, that is Large-Scale Scrum which decided to “choose a vowel” and became known as LeSS.

LeSS emerged in 2005 from the work of Craig Larman and Bas Vodde, early adopters of Scrum who were attempting to scale the framework across multiple teams. In those early days, Larman and Vodde were among the few voices addressing Scrum at scale, pioneering territory with their books and experiments. Over a decade of work involving more than 500 experiments, they discovered something fundamental: the problem wasn’t that Scrum didn’t scale, the problem was that traditional organisational thinking prevented it from scaling.

This insight became the foundation of LeSS. Fewer roles, fewer artefacts, fewer processes. They stripped away the organisational debt accumulated over decades of hierarchical thinking and proposed doing more with less. The framework is deliberately minimal as its primary purpose is descaling through simplification. One product owner, one product backlog, multiple teams working together in coordinated sprints. No scaling roles, artefacts, or ceremonies beyond what teams need to coordinate. LeSS acknowledges it’s not for every business context as it focuses on two clear objectives: building adaptability and delivering customer value.

LeSS describes itself as “barely sufficient methodology”, providing minimal rules to establish empirical process control and whole-product focus, then expecting organisations to think, learn, and adapt. For organisations aligned with these objectives, LeSS offers ten guiding principles with certain mandatory practices that define the start of the journey. Beyond this, there are no detailed prescriptions or step-by-step playbooks. Instead, LeSS provides rules (the minimum framework), principles (the thinking foundation), guides (recommendations worth trying), and experiments (situational options). This isn’t a methodology you implement; it’s a framework that defines a minimum standard and invites you to apply systems thinking and lean thinking to continuously improve your organisation toward your objectives.

So on our spectrum of agile certifications, who is LeSS’ political counterpart? As our far-left progressive agile certification, LeSS is equivalent to The Greens.

The parallels are immediate and striking.

Both emerged from direct experience with key problems being treated as negotiable. The Greens because environmental degradation was compromised away by major parties, LeSS because Larman and Vodde discovered that scaling Scrum required removing organisational impediments, not adding structure. Both demand systemic transformation: The Greens challenge capitalism’s growth imperative and advocate for radical power redistribution; LeSS eliminates command-and-control hierarchies and redistributes authority to self-organising teams.

Both champion grassroots empowerment and systems thinking. Both define a minimum acceptable state and argue that anything less undermines the outcomes they seek to achieve.

Both also share a common challenge: translating a principled vision into change within complex, existing systems. The Greens articulate a clear picture of sustainable societies while facing scrutiny over transition pathways within current economic structures. Similarly, LeSS articulates a clear minimum state for effective agility, while deliberately avoiding prescriptive transformation roadmaps. Both describe a minimum standard for an acceptable state and invites us to confront the gap between the current reality and meeting this standard. For some, this clarity is liberating; for others, it can feel confronting.

This explains why LeSS has such polarising appeal. For organisations genuinely committed to transformation, for leaders willing to challenge their own authority, for teams ready to take on real responsibility, LeSS provides a clear and uncompromising path – it’s honest about what’s required and doesn’t pretend you can have agility without changing power structures. The certifications reflect this philosophy: training will provide you with this acceptable standard, however, if you are operating in a project-led structure even this might seem like an insurmountable barrier.

LeSS appeals to an organisational profile that is looking to optimise towards adaptability and value delivery. If you’re working in a more traditional organisation with entrenched hierarchies, established governance structures, and risk-averse cultures, the radical simplification and structural changes LeSS requires will feel frustratingly disconnected from your reality. This doesn’t mean that LeSS is wrong, it likely means your organisation is optimising toward different objectives. In that case, LeSS becomes a reference point for what agile at scale could look like, rather than a framework that serves your current needs.

In many ways, LeSS resembles the Australian Greens party in politics – it articulates an ambitious, principle-driven vision of how things ought to work, appealing strongly to those who share its values. However, like the Greens operating within Australia’s established political system, LeSS can struggle to gain traction if your worldview is on the right-side of the spectrum.

There’s nothing wrong with unwavering principles and minimum standards. Progress requires people willing to articulate a vision, to refuse compromise, to insist that systemic problems require systemic solutions. The Greens serve this role in politics. LeSS serves this role in the agile political landscape.

For organisations ready to genuinely transform, LeSS might be exactly what you need. For organisations needing to navigating current realities such as command-and-control leadership and heavy bureaucracy, you may need to look elsewhere on the spectrum to address these constraints first. Like its political counterpart, LeSS isn’t trying to win over the pragmatists. It’s trying to inspire the revolutionaries.

Special thanks to Venkatesh Krishnamurthy, Australia’s first Certified LeSS Trainer for his contributions to this article.

Footnote: In this article we specifically focused on LeSS as it fits within our requirement of offering an agile certification, however, we would like to acknowledge its place alongside others in what we have deemed the “ideal state movement”. This entire movement is rich with various approaches addressing work differently. Examples include Holacracy‘s elimination of hierarchy, FAST‘s fluid teaming and network structures, XScale‘s descaling and elimination of command-and-control, and Teal organisations‘ evolutionary purpose made famous in Laloux’s cultural model.

This article was originally published on LinkedIn by Daniel Luschwitz. The next article in the Agile Political Landscape series is: DSDM and Katter’s Australian Party

The Agile Political Landscape Series: PRINCE2 Agile and One Nation

Please note: This is article 2 in a series that explores mapping agile certifications to what we have coined the Agile Political Spectrum. The first blog in the series is What if Agile certifications were a political party?

A note on our political comparisons: These political comparisons are playful metaphors designed to illustrate philosophical positions on the agile spectrum. No certification body was harmed in the making of this analysis.

Every political spectrum needs a far-right party and in the agile certification world, that’s PRINCE2 Agile. The agile extension to a project management methodology called PRojects IN Controlled Environments, version 2 (PRINCE2) wears its conservative credentials openly.

In 1989, a UK government department created PRINCE seeking to protect itself from project failure through rigid process, strong governance and uncompromising control. Updated to PRINCE2 in 1996, these rigorous controls, defined decision points and detailed documentation requirements were designed to provide transparency and auditability considered critical in public-sector environments, but they also made the framework process-heavy and bureaucratic. The approach worked: PRINCE2 became one of the world’s most widely adopted project management frameworks.

Fast forward to 2015. The agile movement had transformed software development and was making inroads into broader business practices. PRINCE2 Agile emerged as an attempt to give organisations a way to adopt agile methods within the PRINCE2 framework. The goal was to preserve the strategic direction, business justification, and stage-gate controls of PRINCE2 while enabling teams to work in a more collaborative, incremental manner. In practice, that meant layering agile practices onto PRINCE2 governance rather than rethinking the underlying assumptions of the framework.

PRINCE2 Agile was launched with scepticism. The agile community rejected it for not being agile enough. The PRINCE2 community worried it was letting go of too much control. Caught between two worlds, PRINCE2 Agile largely satisfied neither.

This is the challenge of compromise and to PeopleCert’s credit, they’ve acknowledged it. In a recent conversation, Markus Bause (VP Product at PeopleCert, the owners of PRINCE2) reflected candidly on this balance. The organisation responded by releasing Version 2, which places greater emphasis on mindset, people and leadership, while significantly improving the learning experience. This is a topic Sean Blunt explored further in his article Agile Leadership: Enabling Government Transformation.

Version 2 offers a broad introduction to agile. It defines the mindset, values and principles and covers several techniques and approaches considered part of an agile toolkit. There are some interesting terminology and structure choices along the way, but overall, it provides a reasonable introduction to the fundamentals of agile project management.

However, as its name suggests, the certification on offer is PRINCE2 + Agile. At the intersection of fundamentally different philosophies, compromise is inevitable. But compromises reveal priorities. PRINCE2 by design prioritises slow, structured, risk-averse progression over speed, experimentation and rapid value delivery. The entire model assumes that careful planning, authorised stages, and methodical oversight are inherently safer than moving quickly, adapting frequently or learning through iteration. PRINCE2 Agile is a compromise that restricts agile to its most conservative form.

So on our spectrum of agile certifications, who is PRINCE2 Agile’s political counterpart? As our far-right conservative, PRINCE2 Agile is equivalent to One Nation.

We now hear the chorus “please explain”.

One Nation is a nationalist, socially conservative party sceptical of change and strong on government control. The parallels to PRINCE2 Agile are striking. Both were born from a desire to protect; One Nation from perceived threats to national identity, PRINCE2 from project failure. Both prioritise control over adaptation. Both are suspicious of external influences that might challenge their worldview and both struggle when reality demands flexibility.

Just as One Nation wants strong government control and has protectionist tendencies, PRINCE2 was born from a government department wanting to protect itself through rigid process and governance. PRINCE2 Agile attempts to liberalise this ideology, to let in some outside influence, but only on its own terms. Agile practices are permitted, but they are constrained to operate within PRINCE2’s governance framework. The conservative DNA remains intact.

This explains why PRINCE2 Agile has such a specific, narrow worldview. It defines how agile can be applied in “projects” and “business-as-usual” but disregards any notion of an operating model where products have continuous lifecycles independent of project boundaries. Like its political counterpart, PRINCE2 Agile knows how the world should work and anything outside that framework somewhat doesn’t exist.

PRINCE2 Agile has a legitimate place in the market, specifically for organisations already operating within the PRINCE2 framework who need to introduce agile project management practices. If you’re in a heavily regulated environment with genuine compliance requirements or working in government contexts where PRINCE2 governance is mandated, PRINCE2 Agile may be exactly what you need to increase speed.

The challenge arises when PRINCE2 Agile becomes someone’s only exposure to agile thinking. You’ll learn about “being agile” over “doing agile”, some agile practices and some lightweight methods but all within a structured project management governance model. You’ll understand iteration but not continuous delivery. You’ll practice ceremonies but not self-organisation. You’ll know agile vocabulary but not agile as a business operating model. It’s a starting point, not the full spectrum.

For practitioners building agile capabilities or organisations genuinely seeking business agility, understand what you’re getting: agile project management within PRINCE2, not agile transformation. There’s nothing wrong with that – as long as it’s intentional.

In the end, PRINCE2 Agile is doing exactly what One Nation does: serving a specific constituency with clear, unwavering views about how things should work. Both have their supporters, both have their critics, and both will insist they’re more flexible than they actually are. If your organisation lives in PRINCE2 territory and needs to introduce some agile practices without causing a governance revolt, PRINCE2 Agile is your candidate. Just don’t expect it to lead a revolution – that’s not what conservatives do. And whatever you do, don’t ask it to “please explain” why everything must fit within project boundaries. You’ll be there for several stage-gates.

This article was originally published on LinkedIn by Daniel Luschwitz. The next article in the Agile Political Landscape series is: LeSS and The Greens

What if Agile Certifications were a Political Party?

Over the last couple of decades, we have been pushing towards agility as a catalyst for a different way of working entirely. It’s interesting to reflect on where agility has ended up today.At the same time, traditional project management approaches talk about agile purely through a project management lens rather than a broader business and product context and as a result we aren’t always speaking the same language. To close that gap, you can use two different phrases:

“Agile within a project management operating model”
“Agility within a product management operating model”

Meeting organisations where they are matters more than ever. The agile industry took four values and twelve principles and somehow created hundreds of methods, wars between approaches, an alphabet soup of certifications, and a handful of enterprise frameworks each claiming to be the silver bullet. We’ve ended up with organisations at vastly different points on their journey and lots (and lots) of confusion in between.

Same word – agile – but very different contexts. Then it occurred to my long-time colleague Daniel Luschwitz, agile is just like politics. Both operate on a continuum left and right of centre. The further away from the centre to the right is a more conservative ideology, whereas to the left is a more progressive ideology.

In agile terms, the centre is the tipping point between:

Project-led agile (right-conservative)
Product-led agile (left-progressive)


Agile even has a constitution – the AgileManifesto. A set of 4 values and 12 principles that mostly any agile approach references and considers itself as following.

We also have a lot of ‘healthy’ debate in both politics and agile. Much like we hear in the halls of parliament “that is unconstitutional”; the agile community has been known to throw a few “that is not agile” phrases around too.

So, all this raises the question: if the various agile certifications were Australian political parties, what party would they be? Who would be our Australian Labor Party, Liberal Party of Australia and The Australian Greens parties? Do we have a contender for Pauline Hanson’s One Nation Party, the Trumpet of Patriots or the Shooters Fishers and Farmers Party?

Where does the various incarnations of Scrum fit in the political landscape? Is SAFe progressive or conservative? Do any agile certifications have their ‘bee in a bonnet’ about paper bags?

To complete this exposé of the agile political world, Daniel Luschwitz brought me in to help write this series, ads, in his words, I am an authority on the agile landscape, “40 agile methods in 40 minutes” creator, and having served on the Agile Alliance Board I am technically a retired agile politician… and we all know what happens when retired politicians talk!

What’s next?

Over the coming posts, Daniel and I plan to map well-known certifications and frameworks across the Agile Political Spectrum.

Why?

It should be a bit of fun. Plus, Daniel has told too many people he plans to write this to back out now.

However, there is a serious side to this. The market is saturated with agile certifications and in many cases participants, managers of teams and recruiters haven’t fully understood what context the certification they have received serves. Our aim is to create awareness.

In the meantime, we welcome you to join in the debate! Who is your far-right conservative agile party?

The first article in the series is: PRINCE2 Agile and One Nation

Note: This article was amended slightly form the original published by Daniel Luchwitz to be written from my perspective.