So, it’s a new year. New year, new start, yadda yadda yadda. Maybe you are considering some New Year's resolutions. I wanted to invite you to take our 2017 waste-loss challenge by decreasing your sabotagile quotient. This challenge builds upon my previous blog, “Agile or Sabotagile: Help Your Management Understand the Difference.” If you haven’t read it yet, please do so and come back.

Before we go further, let’s start with some definitions to help clarify the difference between Agile and sabotagile and introduce the sabotagile quotient.

Here's a couple of definitions.

• Agile: Describes an organization that applies the Agile Manifesto and Principles to enable self-organizing, cross-functional teams that frequently release high quality and incremental business value as a means to gett market feedback that guides future decisions.

• Sabotagile: Describes an organization that applies the Sabotagile Manifesto and Principles to command and control teams into releasing feature-packed releases on unrealistic deadlines, usually sacrificing quality and sustainability and delaying feedback from the market.

• Sabotagile quotient: A number based on empirical evidence that has an inverse co-relation to an organization’s agility. Calculated as follows:

{ ∑(Evidence of Sabotagile Manifesto) + ∑(Evidence of Sabotagile Principles) } x 100

/

1 + {∑(Evidence of Agile Manifesto) + ∑(Evidence of Agile Principles)}

Ranges from 0 (high likelihood of agility) to 1,800 (low likelihood of agility).

Here are a couple of key facts about the sabotagile quotient.

• The sabotagile quotient is calculated on a cadence, at least monthly.

• Members of Agile teams reflect together. Management reflects with peers, i.e., groups of managers, directors, VPs, SVPs, CXOs, etc.

• Each participant has access to the Agile and sabotagile Manifesto and Principles. You can use my slideshare presentation as a reference.

• Each participant maintains two totals: Agile total and sabotagile total.

• Reflect on the retrospective period and compare significant events and decisions to 18 pairs of statements in the Agile and sabotagile Manifesto and Principles.

• There are only two possible scores for each pair of statements: zero or one. For each pair of statements, assign a score as follows:

  • If there were significant sabotagile events or decisions relevant to this category, increment the sabotagile total by one and move on to the next item.

  • If there were significant Agile events or decisions relevant to this category, increment the Agile total by one and move on to the next item.

  • If there were no significant sabotagile or Agile events or decisions relevant to this category, leave the totals unchanged and move on to the next item.

• Calculate the sabotagile quotient:

(Sabotagile Total) x 100

/

1 + (Agile Total) 

It should be a value between zero and 1,800.

• Average the score for the entire team.

Intentional Imperfections

This is an imperfect process and tool by intent. Reminds me of something I once read (I forgot who said or wrote it and Google is not helping much):

“A tool can be a valuable servant but a terrible master.”

There’s plenty of ambiguity.

What may be a significant event or decision for one team member may be insignificant for another. Awesome! What may be an Agile for one team member may be sabotagile for another team. Great!

Let’s use this as an opportunity to value interactions between these individuals over the process and tools.

Exploration

Some food for thought.

• What might the sabotagile quotient tell us about our company?
• How might we apply the sabotagile quotient to increase value, decrease waste, and manage risk for our company?
• What might be some risks and unintended consequences? How might we manage them?

Invitations 

I am ending this article with some invitations.

1. Calculate your company’s sabotagile quotient in your next team retrospective.
2. Compare and contrast perspectives across team members. Disagree without being disagreeable.
3. What would you like your company’s sabotagile quotient to be? Set a target for December 2017.
4. If there was one experiment your team conducted in the next 30 days to help your sabotagile score trend in the desired direction, what would it be?

You can also view this blog as a presentation on Slideshare here.

Let me know what you think and discover.

Until the next article, keep calm and Scrum On!