12 “agile” principles

By Tony Collins

The  principles (below), which are largely managerial,  highlight the challenges for government departments and suppliers of adopting agile principles for major IT-related projects such as Universal Credit.

Some in government have said that agile can deliver systems to support political policy quickly, say within two years –  but that’s far too long. Under agile principles, working systems should be delivered between two weeks and two months.

 I particularly like the tenth principle, which defines simplicity as the art of maximizing the amount of work not done; in other words not gold-plating requirements.

The second principle is also especially important for government IT-enabled projects and programmes: it states that changing requirements are welcome, even late in development.

The principles are from the excellent website of project manager Robert Kelly.

12 Principles behind Agile
  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.
  8. Agile processes promote sustainable development.  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.

Kelly’s contemplation – Robert Kelly’s blog

The Institute foir Government recently produced some case studies from its System Error report.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.