Just having gotten back from Agile 2009, there is a tension in the air that I find interesting in the agile community.


Most people / companies seem to get the mechanics of agile delivery. No one is debating the merits of writing unit tests, gathering requirements as user stories, and delivering functionality incrementally.

People get that.

What is more interesting is how companies, specifically senior management, are reconciling this growing wave of common sense and pragmatism that agile brings to project delivery, as it bubbles up within their organizations.

The tension I am referring to is how companies with traditional command and control style structures reconcile the brutal honesty and visibility agile brings to projects and portfolios.

No longer can management remain blissfully unaware of how their projects are doing. When the true state of a project is revealed, and it conflicts with the edicts and lightning bolts thrown down from up high, some tough conversations will need to be had.

As agile gains in popularity, and the dysfunction of how we have traditionally managed and run projects becomes more clear, it will be harder for command and control style management do just say ‘do it!’, when there is measured, tracked compelling evidence indicating others wise.

So if you’ve had great success with agile at the project level, and you are wondering how to capitalize on this and transition it to the next level, take comfort in knowing that you are not alone. Many are undergoing the same journey.

For some the transition will be smooth.
For others it will never occur.

The good news is that the conversations are occurring. And those companies that make the transition will reap the rewards and benefits that come from having an energized, self-organizing, continuously improving eco-system upon which to build compelling projects and services. And others will continue (some very successfully) with what they have done before.