The Right Way to Use a Manifesto

The Right Way to Use a Manifesto

There are no fewer than 36 “manifestos” out there somewhere, pertaining to Agile, product design, business agility, and a range of related topics.

It seems like creating a manifesto is the thing to do when one has ideas for how to do things better.

This might seem like a bad thing: after all, how does one know which one to follow? Which one is right?

But that question is actually the problem: one should not seek one to follow. A manifesto is not a religious text, assumed to be the “one true word” of a higher power.

Manifestos are written by mortal people, and they are all imperfect.

Manifestos are written by mortal people, and they are all imperfect.

Recently I wrote a post in LinkedIn pointing out that the Agile Manifesto has serious flaws. My post was, I thought, nuanced and thoughtful. I did not wholesale dismiss the Manifesto: I was surgical about what some of its flaws are, and I prefaced my post with the statement that “The Manifesto was a strong document”, and yet, while I received a lot of support (and a ton of LinkedIn connect requests afterwards), I also received a good number of nasty ad hominem responses (though fewer than the number of connect requests that I received).

Such is dealing with the public: there are those in the public who will throw stones when they don’t like what you say, and will seek to sew chaos and make broad statements such as “this is a mess” or “none of this makes sense”. That is highly unpleasant, but it is not disagreement that is unpleasant – what is unpleasant is nastiness.

The good news is that the nasty people will be unable to actually hone in on what they don’t like, because their reaction is driven by emotion – not logic.

The people who hurled nasty responses were, I believe, those who have come to identify with the Agile Manifesto on a personal or professional level: by critiquing the Manifesto, I was – in their mind – critiquing them or their work.

That is a real problem, because if people identify with documents or sets of ideas, then we cannot criticize those without offending people personally. That prevents us from advancing.

Einstein had this problem: during his early career there were many scientists who had built careers around teaching Newtonian Mechanics. Relativity challenged that, and they took it personally, and they were pretty vicious towards him.

Some say that science advances one death at a time: in other words, we have to wait for the current theories’ proponents to pass on before we can challenge those theories.

The solution is the view a manifesto, or any document or set of ideas, as just that: a set of ideas. And presume the ideas to be imperfect. Never, ever come to view the ideas as sacrosanct. And don’t let yourself identify with the ideas personally or professionally: always view the ideas as tools, and anticipate that better tools will come along.

So having multiple manifestos is okay. Each is only a set of ideas. They may overlap – that is okay. And they might even contradict each other, and that is okay too, because they are just ideas, not inviolable rules, and so it is up to you to decide how to apply the ideas, or to decide that they do not apply in your current situation.

One thing that really helps is if a manifesto contains an explanation of the intentions and rationale behind each of its statements. That way, one can grasp the thinking behind it, which enables one to interpret the idea for one’s situation. Lacking an explanatory narrative, one has no choice but to take the idea at face value, and apply it without adjustment. And that is a hugely risky thing to do: it effectively turns the manifesto into a set of rules, which it should never be.

So beware manifestos that contain merely a set of unsupported assertions. And if you cannot feel confident that you understand the manifesto’s ideas – that you have not experienced situations in which its ideas apply – then you are not ready to use those ideas.

Sumeet Gayathri Moghe

Author | AI consultant | Product manager | Agile coach | Future of work strategist | Collaboration expert | KM + L&D geek | Director of communications | Photographer

2 年

Cliff Berg the backlash you mention and some of the caustic comments I see on this thread tell me something. It's that some of us believe that in 21 years we'd have learned something new. And some of us believe that time stopped still at the manifesto and everything that was true then, is still true today. I know which side I stand on. And for that I'm glad.

Rita Helgenberg, CSM, CRTE, LSSMBB

Agile Professional, GE Master Black Belt, Industrial Engineer

2 年

If using the manifesto doesn’t work for your teams, just coach with Lean. Same thing.

回复
Christopher Vestal

Turning chaos into clarity and confusion into momentum.

2 年

"It does not say, "Forget process and tools -- only pay attention to individuals and interactions." Instead, it says, consider both, but pay special attention to individuals and interactions. In other words, the Agile Manifesto advocated judgment and consideration of context. In that sense, it is a sophisticated document and cannot be used well by people who do not have the experience needed to apply judgement." - Cliff Berg (Agile 2)

Erik Kraa

Scrum Master. Mijn woorden zijn van mij, die gebruik ik op privé titel.

2 年

Very sad for such a talented man. If you have nothing positive to say, than please stay silent. Im sorry Cliff Berg but you are acting more and more as a disgruntled man.

W?odzimierz Ko?odenny

Project Manager| Agile Project Manager

2 年

I find agile manifesto one of the best texts written ever. It's a clean, generic way of description. If someone needs a prescription, they should go to a doctor.

要查看或添加评论,请登录

Cliff Berg的更多文章

  • They Know a Collapse Is Coming

    They Know a Collapse Is Coming

    The CIO of Goldman Sachs has said that in the next year, companies at the forefront will begin to use AI agents as if…

    78 条评论
  • Agile – I Told You So

    Agile – I Told You So

    I think it is no longer controversial that the Agile movement is in decline. When I made a post about it a year ago…

    51 条评论
  • The Most Brilliant Programmer I Have Known Couldn't Work at Google

    The Most Brilliant Programmer I Have Known Couldn't Work at Google

    During the late 1980s I worked at a 30-person startup. The company was founded by the two fellows who had been the lead…

    31 条评论
  • The Most Guaranteed Way to Improve the Bottom Line

    The Most Guaranteed Way to Improve the Bottom Line

    Culture eats strategy for breakfast, but it’s leaders who generate the culture – leaders at all levels, not just at the…

    2 条评论
  • Empowerment, Not Self-Organization

    Empowerment, Not Self-Organization

    Have you heard people say something to the effect of, “Self organization is not really entirely self organization”? I…

    11 条评论
  • Join a Community that is About Learning

    Join a Community that is About Learning

    Things like leadership, product development, technical practices in DevOps, and more. Free workshops for learning.

  • Anyone Can Learn DevOps

    Anyone Can Learn DevOps

    Are you looking for ways to expand your skills, to be more effective in your organization? One way is to learn more…

  • Use a Capability-Focused Approach — Not an Agile Framework

    Use a Capability-Focused Approach — Not an Agile Framework

    Article here: https://www.agile2academy.

    3 条评论
  • Why Team Performance Is the Wrong Thing to Focus On

    Why Team Performance Is the Wrong Thing to Focus On

    Many companies today are obsessed with teams. The “old” approach of static departments and hierarchies is out.

    12 条评论
  • Leadership Is the Key Skill Today

    Leadership Is the Key Skill Today

    Join our free “Intro” to our acclaimed course, Constructive Agility? for Leaders. (Formerly Agile 2 Foundations) It…

    5 条评论

社区洞察

其他会员也浏览了