Tag Archives: unagile manifesto

The Un-Agile Principles

These are the Unagile Principles also known as the Principles Behind the Unagile Manifesto. They are a support for all those who oppose the dangerous and wide-spread dissemination of methods based on the principles behind the Agile Manifesto.

  • Our highest priority is to satisfy the customer through delivery of the contracted software on or after the date when the customer is ready to receive it.
  • Welcome changing requirements, even late in development. Unagile processes harness change for the suppliers profit through additional costs for each request.
  • Deliver working software as specified in the contract with a preference for a big bang at the end of the project.
  • Business people and developers must interact at times during the project. This should be kept to a minimum.
  • Build projects around exchangeble individuals. Give them the supervision they need, and watch them to get the job done.
  • The most efficient and effective method of conveying information to and within a development team is through comprehensive reviewed and audited documents.
  • Milestone deliveries of essential documentation is the primary measure of progress.
  • Unagile processes promote sustainable development. The underlings should be required to maintain a high pace indefinitely.
  • Attention to technical excellence and good design in appropriate phases of a project enhances unagility.
  • Complexity–the art of maximizing the match between the work done and the complexity of real life–is essential.
  • The best architectures, requirements, and designs emerge from carefully selected teams of experts.
  • At post-mortem, the managemnt team reflects on how to become more effective, then tunes and adjusts the behavior of their underlings accordingly.

Un-Agile Manifesto – when you hate agile

A fisted hand holding two lightning bolts to symbolize the un-agile manifesto
Time to take a stand against Agile… Sign the un-agile manifesto…
(Image used as public domain image, click image for license details.)

The so called Agile Manifesto has created so much excitement in the software development world and beyond. But for all those who got their life ruined by agile, for all those who oppose Agile methods in software development — it is time they got their own manifesto. Here it is — The un-agile manifesto.

The Un-agile Manifesto

We are rediscovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:

  • Follwing a plan over responding to change
  • Contract negotation over customer collaboration
  • Comprehensive documentation over working software
  • Process and tools over individuals and interactions

That is, while there is some supposed value in the items on the right, we value the items on the left more. The Unagile Manifesto is based on the Unagile Principles.

Rationale

Following a Plan

Responding to change is a bit of a joke. We known since time immemorial that there are no changes. “There is nothing new under the sun.” So what is change? It is just an attempt to create confusion and sabotage the project. It is better to stick to the plan.

Contract Negotiation

Customer collaboration is just another way to try to introduce changes into the project. A contract is what you have to guarantee to yourself and the customer that they get exactly what they pay for.

Comprehensive Documentation

How long will your software keep working if it is not documented?

Process and Tools

In hobby-sized projects people can chat and be nice, in industrial strength projects it is necessary to use processes and tools to align people and products.

This post was updated on 2013-12-18 with a rationale for each item in the manifesto.