Articles 1 min read

You’re not doing Agile unless you know the Manifesto by Gareth Baxendale

Like many frameworks and methodologies, it’s all too easy to wave the flag claiming to be a dedicated follower and implementer of ‘good practise’. Many will triumphantly say “Yes, we follow X methods at our business” while being blissfully unaware of what this really means.

Consider software development and the Agile approach. Many understand the clear benefits when compared against a Waterfall approach, many love the idea of ‘sprints’ and ‘scrums’ but how many know that a detailed manifesto exists for Agile? That the manifesto is underpinned by 12 principles?

If this is news to you then hop along to http://agilemanifesto.org/ where you will find a clearly defined manifesto that is now some 13 years old!

The 12 principles underpinning the manifesto are:

1 – Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

2 – Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.

3 – Deliver working software frequently, from a couple of weeks to a couple of months, with a 
preference to the shorter timescale.

4 – Business people and developers must work together daily throughout the project.

5 – Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

6 – The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

7 – Working software is the primary measure of progress. Agile processes promote sustainable development.

8 – The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

9 – Continuous attention to technical excellence and good design enhances agility.

10 – Simplicity–the art of maximizing the amount of work not done–is essential.

11 – The best architectures, requirements, and designs emerge from self-organizing teams.

12 – At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

The next time someone tells you they ‘do Agile’ ask them to recite the above principles and if they fail chase them out with a pitch-fork and tell them never to return.

If you really want to show your support for the Agile Manifesto why not sign your name on the site and tell the world why you think it’s important, you know you want to.

The Business Transformation has posted this article in partnership with ITwaffle.com.

 

Hear it first

Stay up to date with our latest content and events

Watch, read or listen to content from the brightest leaders across the world of People, Process & Technology.

Find out about the latest events across Europe

Network with like-minded professionals in your industry

Find and apply for the best jobs

See content that you like?

Share your experience by joining your exclusive roundtables, or contribute to our content like industry peers.

Get involved