Skip to main content

The Agile Late Majority has different needs

Are we applying a great solutions to a poorly understood problem?   What is the question - we know the answer is 42.

The early adopters of Scrum were seeking a method of controlling the chaos of emergent product development processes.  They needed empirical methods to discern if the product was moving in a meaningful direction.  They were willing to risk accepting technical debt to validate working solutions in the hands of real customers.  They were focused on delivering value, they wanted a process that optimized on value delivery and embraced the learning process required to explore new product domains.  They were organizations capable of thriving on the edge of chaos.  Organizations in the early adopters phase seek to keep options open (decide at the last responsible moment), to pivot  upon learning about the opening market space, to fulfill an undefined emergent need.

"Intelligence should be viewed as a physical process that tries to maximize future freedom of action and avoid constraints in its own future." -- Alex Wissner-Gross

Tardigrade - an extremophile
These organizations are perhaps a small subset of all corporations - perhaps these are extreme examples - but they exist.

But extremophiles do not live in the calm waters of the Caribbean reef.

"Most executives I’m meeting with nowadays aren’t fundamentally trying to solve the adaptability problem." 
-- Mike Cottmeyer - Are we Solving the right problem? 

The Agile movement has reached the late majority of the diffusion of innovation curve.

The Late Majority:  "Individuals in this category will adopt an innovation after the average member of the society. These individuals approach an innovation with a high degree of skepticism and after the majority of society has adopted the innovation. Late Majority are typically skeptical about an innovation, have below average social status, very little financial liquidity, in contact with others in late majority and early majority, very little opinion leadership." -- Everett Rogers

My opinion is that this group is seeking a different answer than the early adopters or early majority.  Studying Rogers' diffusion curve and synthesizing some other really observant human behavioral ideas; I think it's very obvious that the late majority have a very different answer to the fundamental questions around why they are adopting Scrum.  I've asked this question for years in workshops.  The answer's haven't changed.  But the meaning behind the answers must be different than they were before.

Is it the value system of Agile that draws these companies into the Scrum trainers classroom?  No.  Is it the promise of the more collaborative and humane software development lifecycle for the employees?  No, many of these companies have already shed their employees by adopting the staff augmentation model of the 20th C. consultant/contractor model.

The answer this group of late majority scrum adopters are seeking is: a lowering of the cost of development and maintenance of software systems that run and maintain the business.  Very few projects that these organizations attempt are in the domain of seeking an innovative or emergent solution.  Sure they speak the current lingo of innovations but few are seeking disruptive innovation (what must of us think when the "I" word is mentioned), most are seeking frugal innovation (15 Types of innovation).

"Frugal Innovation is about doing more with less. Entrepreneurs and innovators in emerging markets have to devise low cost strategies to either tap or circumvent institutional complexities and resource limitations to innovate, develop and deliver products and services to low income users with little purchasing power."

This group is not seeking to open up the future options that an emergent process may afford them.

See Mike Cottmeyer's blog series What Problems Are Executives Trying To Solve With Agile?  It is a very good list - if you need an answer, pick one from his list - it's sure to impress.

Start with WHY - Simon Sinek
Perhaps we should start our agile transition with a serious question - Why?

I've asked this question, but just getting a few mid-level managers and the executive level sponsor answering this question may not be enough.  Is there a method of hearing the organization - rather than the designated spokesperson for the organization?  Enter Open Space Technology.  Why yes, yes I believe this may provide a collaborative way to answer the question without the filter imposed by a leadership visor.  Inside of the Agile movement it may best be expressed by Open Agile Adoption techniques.

Is Agile a solution for this cost reduction and predictable deliver of replacement solution domain of the late adoption mindset?  I believe they can see benefits of adopting the basic foundations of Scrum.  Of adapting the underlying Extreme Programming techniques that power the Scrum framework.  Yet the agility of the processes might be antithetical to the organizations purpose of delivering software.

A case in point:  a client in the data management of health care actually has the policy of allowing their clients to pick and choose (ala-carte) the software development process aspects that they are willing to pay for.  For example - the client may not wish to pay for the QA on a project, so the development group conceives that it is their role to deliver a software product without doing the QA.  Or perhaps the client doesn't want to pay for the project management aspect, or the architectural analysis of the solution.  Now this is an extreme situation - true.  One that none of us would like to be in - but can this organization adopt the Agile mind-set?  When the various directors and VPs of this organization say they want to do the Scrum/Agile thing - do they mean what I think they mean - or are we talking about very different purposes?

Alex Wissner-Gross - A new equation of intelligence - TED Talk







Agile Scout's SAFe Review

Agile Has Not Crossed the Chasm, a contrarian view by Johanna Rothman 2012 and still relevant:
Bounce Back is too CommonHere’s the problem I see. We’ve seen several consultants and consulting organizations take the credit for the same large media organization succeed with their agile transition. Well, this same organization is on their fourth or fifth agile transition by now. They have the common problems of any significant process change: it’s difficult, culturally challenging, and the entropy of the organization is working against them. It’s easier to bounce back to chaos or waterfall

HBR article:  Embracing Agile  2016
by  Darrell K. RigbyJeff SutherlandHirotaka Takeuchi
Agile innovation methods have revolutionized information technology. Over the past 25 to 30 years they have greatly increased success rates in software development, improved quality and speed to market, and boosted the motivation and productivity of IT teams.

David vs. Goliath no more, Agile adoption is the new standard. by Joseph Flahiff - July, 2017
As Agile adoption grows, companies should not be looking to specialists to support agility, says Joseph Flahiff. Make Agile coaching a standard job requirement for team managers.
Post a Comment

Most Popular on Agile Complexification Inverter

Where is Shakespeare When We Need Him?

We are desperately searching for a term for people that connotes the best of human kind.  The creative, sensing, combinatorial synergistic, empathic solutioning persons that have yet to been labeled with a role name that works.

Some of the old terms:
Staff, Workforce, Human Resource, My Team, Army, Company

Shakespeare created 1700 words in his time.  He mutated verbs to nouns, and vice-a-versa, transformed verbs into adjectives, and formed words from whole cloth never before heard.  This skill is rare, but there is a poet that can create the term we need in the twenty-first century.

What should this term define?

21st Century Human Resource; the generalizing specialist.

Yes, but what more?  What less?

Suggest your poetry in the comments, let us see if we cannot do 1/1700 as well as The Bard.

By-the-way; who create the phrase "coin a word"?



A TED Play List - How do you create new words
6:52
Erin McKeanGo ahead, make up new words! In this fun, short talk from TEDYouth, lexicographer Er…

Elements of an Effective Scrum Task Board

What are the individual elements that make a Scrum task board effective for the team and the leadership of the team?  There are a few basic elements that are quite obvious when you have seen a few good Scrum boards... but there are some other elements that appear to elude even the most servant of leaders of Scrum teams.









In general I'm referring to a physical Scrum board.  Although software applications will replicated may of the elements of a good Scrum board there will be affordances that are not easily replicated.  And software applications offer features not easily implemented in the physical domain also.





Scrum Info Radiator Checklist (PDF) Basic Elements
Board Framework - columns and rows laid out in bold colors (blue tape works well)
Attributes:  space for the total number of stickies that will need to belong in each cell of the matrix;  lines that are not easy eroded, but are also easy to replace;  see Orientation.

Columns (or Rows) - labeled
    Stories
    To Do
    Work In P…

Situational Leadership II Model & Theory

Have you ever been in a situation where you thought the technique needed to move forward was one thing, yet the person leading (your leader) assumed something else was what was needed?  Did you feel misaligned, unheard, marginalized?  Would you believe that 54% of all leaders only use ONE style of leadership - regardless of the situation?  Does that one style of leading work well for the many levels of development we see on a team?

Perhaps your team should investigate one of the most widely used leadership models in the world ("used to train over 5 million managers in the world’s most respected organizations").  And it's not just for the leaders.  The training is most effective when everyone receives the training and uses the model.  The use of a ubiquitous language on your team is a collaboration accelerator.  When everyone is using the same mental model, speaking the same vernacular hours of frustration and discussion may be curtailed, and alignment achieved, outcomes …

One Dark and Stormy during a Hurricane

I'm from the Carolina's where legend has it that our family commonly just hunkered down in the home on the coast and waterways than to head for inland shelter. Now that's from the old school days of barely improved (read paved) roads. They counted a storms severity by how high on the back porch steps (about 15 - top to ground) the water reached.  I don't recommend this action in todays world of long range forecast and transportation options.

I do recommend a drink or two in a hotel bar, far far away.

This is the week that Harvey came ashore in Texas.  I live on a hill in the little old town of Grapevine outside Dallas and Fort Worth.  And thank you all for letting me know that a storm is coming... I didn't get out and walk Malibu before the rain hit, so I grabbed a hat and we went anyway.  Much nicer walk with the drizzle, I'd say.

I'll raise a glass to you - if you were not smart enough to do the responsible thing, at the last responsible moment.

I do re…

Software Development terms applied to Home Construction

Let's Invert the typically wrong headed view of Software Development project management as a construction project.  We can map it the other way just to see if it works... to have some fun, to explore the meaning of phrases we toss around quite frequently.


Normally Project Management terms come from a construction domain.  We are going to apply the lexicon of modern software to the construction of a home.  We will follow the construction project and meet some of the people doing the work.

This is a very small (8 homes from $600,000 skyward) program in my 30-40 year old neighborhood.

About 6 months ago I saw the programs landing page go up.  It gives casual observers and some of the stakeholders a general idea of the intent of the program.  And most importantly who to contact for additional information if you happen to be interested in their products.

The Refuge program has 8 product projects and has them running independently.  Yet much of their DevOps infrastructure has already b…