Manifesto for Anti-Agile Software Development — Principles

Principles behind the Anti-Agile Manifesto

Image Credit: Manifesto for Agile Software Development

We follow these principles:

1. Our highest priority is to satisfy ourselves through late and sporadic delivery of mediocre software.
2. Reject changing requirements, yet be late in development. Anti-agile processes resist change until it becomes urgent, for our own convenience.
3. Deliver buggy software rarely, from a couple of quarters to a couple of years, with a preference to the longer timescale.
4. Business people and developers must work separately throughout the project.
5. Conduct projects using demotivated human resources. Give them the minimum resources and support they need, and micromanage them to keep them busy.
6. The most efficient and effective method of overloading the development team with information, without communicating with them, is via text or recorded message passed from many intermediaries.
7. Working software is irrelevant; obsolete documentation and made up reports are the primary measure of progress.
8. Anti-agile processes promote unsustainable development. The sponsors, developers, and workers should be exhausted by constant pressure and overtime.
9. Ignore technical…