Lean-Agile Values Compared

Today, for my own personal growth and agile learning, I gathered values from the most known lean-agile and scaled frameworks. I’ll publish this, in case someone wants to refresh their memory on the values.

“Try not to become a man of success. Rather become a man of value.”
― Albert Einstein

For the sake of succinctness, I made some adaptations along the way. This process posed some brain-teasers, since some frameworks do not disclose their values, but talk about principles instead. The way I interpreted values and principles for this exercise, was to take values as immutable and principles as mutable. In other words, I take that values can change over time, where as principle are systemically universal and fixed.

I aimed for maximum of five short value descriptions per method, if possible. I may have made mistakes and/or harsh adaptations to reach this goal. Here’s hoping I didn’t murder any frameworks along the way.

For example Kanban-values in the table are my own interpretations, therefore marked with (*). However, in text, I do list more authoritative sources. If I was uncertain about some values, I at least tried to be transparent about how I made the decisions. Digest responsibly.

Pre-Agile Values

Waterfall

Waterfall doesn’t have values, if there were, they’s focus around planning and manpower. However, I don’t feel it’s needed to talk trash about waterfall in 2018 – so I’ll just let this part be.

RUP (Rational Unified Process)

Values adapted from RUP’s best practices:

  • Iterations
  • Visuality
  • Quality
  • Control

 

Lean-Agile Values

 

Screen Shot 2018-01-19 at 09.56.24.png

Agile (left-side)

From manifesto:

  • Individuals and interactions
  • Working software
  • Customer collaboration
  • Responding to change

or just very succinctly (thanks for the tip, Tomas Björkholm):

  • Collaboration
  • Responding to Change

 

Agile (right-side)

  • Processes and tools
  • Comprehensive documentation
  • Contract negotiation
  • Following a plan

 

DevOps

Devops builds upon Agile and Lean values, but doesn’t disclose any official ones. Here some adapted from M. Palaniachari’s Slide deck and S. MacTaggart’s post:

  • Culture of Trust
  • Embrace failure
  • Automation
  • Diversity

 

Scrum

  • Commitment
  • Courage
  • Focus
  • Openness
  • Respect

 

Kanban

My list (*):

  • Flexibility
  • Focus
  • Flow
  • Transparency
  • Satisfaction

David J. Anderson’s:

  • Transparency
  • Balance
  • Collaboration
  • Customer Focus
  • Flow
  • Leadership
  • Understanding
  • Agreement
  • Respect

David J. Anderson’s very succinct summary:

  • Respect

 

XP

  • Communication
  • Simplicity
  • Feedback
  • Courage
  • Respect

 

Lean

Values adapted from Lean Enterprise Institute’s 5 Lean principles:

  • Value
  • Flow
  • Pull
  • Perfection

Lean Systems society’s Lean values (copied from B. Sathram’s LinkedIn posting):

  • Accept the human condition
  • Accept that complexity & uncertainty are natural to knowledge work
  • Work towards a better Economic Outcome
  • While enabling a better Sociological Outcome
  • Seek, embrace & question ideas from a wide range of disciplines
  • A values-based community enhances the speed & depth of positive change

 

Lean Software Development

Values adapted from LeanKit’s 7 Lean principles:

  • Holism
  • Quality
  • Pace
  • Knowledge
  • Commitment
  • Respect

 

Scaled-Agile Values

These are the values for scaled frameworks. Summary

Screen Shot 2018-01-19 at 09.56.43.png

LeSS (Large-Scale Scrum)

Builds upon Scrum, so Scrum values apply. However, LeSS doesn’t list values, but principles, and I’ve taken a freedom to interpret a little with bold text:

  • Commitment
  • Courage
  • Whole Product Focus
  • Openness
  • Respect
  • Transparency

 

SAFe

  • Alignment
  • Built-in quality
  • Transparency
  • Program execution

 

Nexus

Nexus guide doesn’t specifically mention values. However some other articles do refer Nexus adopting scrum values, so these’d apply:

  • Commitment
  • Courage
  • Focus
  • Openness
  • Respect

 

DAD

  • Viability
  • Participation
  • Sufficiency
  • Pragmatism

 

That’s all for now. Stay agile.

 

 

 

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s