Why Agile is so important - Part 2

A quick search on Google will show how Agile (in all its flavors) has become very "in, hot, cool, faddish". I had a conversation recently with a long-term bureaucrat who believed that "Agile Bureaucracy" was a possible option for bloated and non-responsive government service! Even EDS with its 100,000 plus people has an Agile model. It won't be long before all major multi-national consultancies will have instant Agile experts.

So, what do we see as Agile.

In our client base, Agile models include three related and evolving elements. The first is Agile Sponsorship/Governance. This covers the linking of change and projects to the organization's Strategic Plan or Outcomes as well as prioritizing projects, executive management of major projects and the management of benefits realization and on-going support. The second element is Agile Project Management (often termed Extreme or Radical) which involves an open and inclusive approach to stakeholder control of their projects and the use of RApid Planning (RAP) sessions developed by our company over the past 20 years. Finally, there is Agile Development (SCRUM, DSDM, etc) which has evolved from RAD, timeboxing and JAD approaches in the mid-1980's. Agile Development involves highly-focussed development cycles of a month or less.

However, all these three elements are bound by the principles of Simplicity and Transparency.

In our next Blog, we'll begin to explore the underlying cultural challenge facing those people and organizations who wish to really implement Agile.