Oct 12, 2017

No Such Thing as ‘The Four Agile Values’

Everyone should just stop referring to ‘The Four Agile Values’ or ‘The Four Values of the Agile Manifesto” 
We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

That is, while there is value in the items on the right, we value the items on the left more.

Why? Because this so-called 'The 4 Agile Values' does not exist.

Consider the following:

1. There Are 8 Values Listed in the Manifesto

If by ‘4 Values’ is meant the following: 

  1. ‘Individuals and interactions’, 
  2. ‘Working software’, 
  3. ‘Customer collaboration’, and 
  4. ‘Responding to change’
Then please note we have eight values listed (not four): 4 values on the left plus 4 values on the right, making a total of eight values.

The manifesto affirms: 'there is value' to the four items on the right. So if you regard the items on the left as values, you need to regard the items on the right as values too. We value family over careers. Does that mean we don’t value careers?

The authors did not put worthless items on the right: 'Customer collaboration over cheating the customer'

They also did not say 'Individuals and interactions, etc' trump everything (see point number 3 below).

2. The 'Values' Are Merely Trade-off Preferences

If you consider the 4 values to be the 4 listed earlier, then please note that these are simply statements of relative value, not of highest value.  Hence, they do not merit the definite article 'The'.

Read them as saying, “between responding to change and following a plan, we regard the former more important”. (How much more important is not indicated).

The signatories shared interesting trade-offs they have ‘come to value’, trade-offs that upend (what they consider) the normative trade-offs in software development. No suggestion is made that these are the only trade-offs they value, nor even the most important ones, but merely the tradeoffs that make their approach different. 

3. The Principles List Even More, Even More Important Agile Values

The Twelve Principles call out other ideas important to the signatories (and by extension to Agile development): customer satisfaction, continuous delivery, frequent delivery, motivated individuals, support, trust, face-to-face conversation, measure of progress, working software, sustainable development, technical excellence, good design, simplicity, best architecture, best requirements, best designs, team effectiveness. Some of these arguably carry equal, arguably even more, weight to the ‘4 Agile Values’.

The first sentence of the manifesto also mentions two ideas valued by the signatories: 'doing it' and 'helping others do it'

4 The Manifesto Never Talks About 'Values'

The manifesto never uses the word 'value' as used in the phrase 'The 4 Agile Values'. In that phrase, 'Value' is a noun that means 'something intrinsically desirable'. These refer to ideas like 'emotional intelligence', or 'integrity'.

The manifesto says that the signatories have come to ‘value’ A over B. The word ‘value’ here is not the same word as the noun. This verb means ‘to consider highly’, as used in 'we value efficiency'. Valuing something does not necessarily turn that thing into a 'value': I have come to value good quality leather shoes over cheap shoes, but good quality leather shoes isn't one of my values.

The manifesto uses 'value' as a noun when it speaks of "there is value..." but this noun carries the different meaning of 'having worth' (the opposite of the word 'worthless'), like gold has value to a jeweler, but dirt does not.

In short, the manifesto never talks of 'values'.

5. Surely There Are Now More Than Four!

The verb tenses in “we are uncovering…” and “we have come to value” indicate that the list is preliminary, and describes a point-in-time state of affairs that is hoped will continue onward. It would be surprising (shocking) if they meant for it to be the final uncovered preferences for all time (or even for a few years).

Referring to 'The 4 Agile Values' after so many years is a serious indictment of the movement, for it means no new Agile-specific value trade-off have been ‘uncovered’ since 2001. (Calling them ‘The Original 4 Agile Values’ would still be wrong -- see points 1 and 2).

Fnally, referring to 'The 4 Agile Values' surrounds them with an aura of being untouchable and unchange-able.

So please stop talking about 'The 4 Agile Values', because doing so promotes misunderstanding and inhibits uncovering of new 'better ways of developing software'


 

    Oct 9, 2017

    6 Simple Rules of Motivation

    Motivating people is really simple. Just base your actions on these 6 simple rules:

    The 6 Simple Rules of Motivation:

    The motivated can make the impossible achievable.

    The unmotivated can make the achievable impossible.

    HOWEVER...

    The impossible to achieve can make the motivated unmotivated.

    The easy to achieve can make the unmotivated motivated

    BUT THEN...

    The "impossible to achieve" can make the unmotivated motivated

    The easy to achieve can make the motivated unmotivated.


    It's really that simple.

    ***

    Aug 27, 2017

    Milestone Sprint

     Idea: a sprint that when it delivers its increment, the overall delivered product has reached an important milestone.  It could be that it has reached an MVP stage and can be delivered (though would not be commercially successful), or can be deployed and actually deliver new capability.  

    Sprints are all meant to ‘deliver’ business value, but realistically most of them just showcase the increment.  The increment often remains unusable.

    Aug 26, 2017

    The Delivery That Stopped The World

    There is an implicit assumption that the world stops changing when the Agile-built product is delivered.

    The argument for Agile over Waterfall is that the world and the requirements change while the product is being built. Agile actually accommodates this change (true). But the world doesn’t stop changing just because we delivered, so a post project ongoing development may need to be planned for.

    Irate at Rate of Learning

    More important than rate of learning is ‘are you learning the right thing’?

    Agile Uber Alles

    How did words from a 2-day meeting at a ski lodge, on principles for a new approach to building software become such gospel that they are now being used as principles to run whole corporations engaged in activities nothing to do with software?   The Agile Manifesto principles are not even the best choice for all types software development.

    This is a fascinating phenomenon worthy of study.  At the very least it can confirm theories about diffusion of untested practices and fads. A generation from now, indiscriminate and inappropriate applications of the Agile Manifesto will be seen as something of a Tulip Mania. Or a YAF.  Yet Another Fad.


    Post Excellence

    When all the competition has achieved excellence, what is the next competitive arena?

    Agile Diversity Manifesto

    To accommodate the (irrational) demands for diversity that is proportional to the wider population, should the Agile Manifesto be rewritten by a new group more diverse than the original set of: 

    1. White 
    2. Middle-aged
    3. Men
    4. Software Developers

    Aug 22, 2017

    A Project is in the Eyes of the Beholder

    A project is a project in the eyes of the beholder,  not an objective character of the undertaking, because the same undertaking can be routine to you, a little bit unique to me, and incredibly daunting to another.  Project management is designed to help you cope with undertakings that (to you) meet the criteria of a project. 

    Aug 21, 2017

    Impact of the World on Technology

    At a training course, the facilitator asked the audience to consider the impact of technology on the world, how technology shrinks and disrupts the world.  

    I thought about the opposite: the impact of the world on technology. With increasing easy access to technology, all the different cultures, all the different ways of thinking, all the different experiences provide solutions to needs that are relatively unimportant to much of the West.

    Think about rat-proof telecom cables from Huawei that Western telecom companies did not come up with for whatever reason. Think about ultra compact white appliances from Haier that Chinese students needed because they live in tiny accommodations. Think abour the mobile payment system from M-Pesa and increasing thousands of other examples.

    The way these applications of technology from other parts of the world have an impact on the technology the West is developing.