Organizational Views of Agile Maturity

From the Voices on Project Management Blog
by , , , , , , , , , , , , , , , , , , , , , ,
Voices on Project Management offers insights, tips, advice and personal stories from project managers in different regions and industries. The goal is to get you thinking, and spark a discussion. So, if you read something that you agree with--or even disagree with--leave a comment.

About this Blog


View Posts By:

Cameron McGaughy
Marian Haus
Lynda Bourne
Lung-Hung Chou
Bernadine Douglas
Conrado Morlan
Kevin Korterud
Peter Tarhanidis
Vivek Prakash
Cyndee Miller
David Wakeman
Jen Skrabak
Mario Trentim
Shobhna Raghupathy
Roberto Toledo
Joanna Newman
Christian Bisson
Linda Agyapong
Jess Tayel
Rex Holmlin
Ramiro Rodrigues
Taralyn Frasqueri-Molina
Wanda Curlee

Recent Posts

Mix & Match

Agile Evolves

3 Tips to Enhance Your Leadership IQ

3 Tips for Becoming a Better Listener—and a Better Project Manager

Maximizing the Value of Agile

Categories: Agile

The desire for organizational agility is on the rise, according to PMI's 2012 Pulse of the Profession.

The survey found that more than 25 percent of respondents now use agile project techniques frequently, and that number is likely to keep moving up. The survey also found that in successful organizations, 68 percent of projects meeting original goals and business intent often used agile project management.

But how does agile apply not just to teams but to organizations as a whole?

When an agile adoption is new, the focus is on training. When teams have been trained, shift your emphasis to fostering a community of agile practice in your organization. As agile matures, the metrics will expand beyond how many people use agile. The metrics will start to verify that agile benefits are beginning to be realized.

These tips can help an organization assess the strengths and deficiencies of its agile teams:

1. Instead of asking about one team's remaining work at the end of an iteration, look at the amount for unfinished work for all teams in your organization. This can tell you who needs more coaching.

Graph the remaining work for each team every two weeks, for example. Can you see which teams need more help? Can you find the average slope for both successful and unsuccessful iterations? Ideally, we start at 100 percent work planned on day one, reach 50 percent in the middle and have 0 percent left at the end of the iteration.

2. Determine if all of your project teams are adding requirements. This can tell you if you are implementing the letter of agile, but not the intent. Strong agile teams will capture some competitive advantage of timely requirements, but will control scope change to not lose focus.

3. Get a pulse on impediments and retrospective actions for all teams.This can tell you if teams are implementing continuous improvement and facing risks head on.

Asking these questions at an organizational level may not be natural at first. But when encouraged, it can reveal a new perspective on which teams are actually leveraging agile as they mature on their path to adoption.

What are your thoughts on organizational agility?

To discuss Pulse of the Profession on Twitter, please use #pmipulse.

See more on the Pulse of the Profession.

Posted by William Krebs on: August 02, 2012 12:37 PM | Permalink

Comments (1)

Please login or join to subscribe to this item
QA Thought Leaders
"The Overall value proposition of IT project is significant and is based on business risk involved. Hence it’s necessary to estimate correctly the duration or complexity of design task as well as changing business needs. Agile development promotes adaptive planning, iterative approach and incremental development that favor rapid response to change and helps in reducing business risk by repeatable testing and automation.

Agile Model does not take enough time to gather empirical evidences and hence estimate the risk through the measure of velocity per iteration. And then it breaks the project into modules called iterations that can be accepted and tested by the user easily and any form of improvement and business values can be added to it. Final integration of all the modules can be done after testing individual one and hence it eliminates the continuous integration and test driven development. Agile approach theoretically makes sense and practically reduces business risk by flexible incremental delivery."

Please Login/Register to leave a comment.


Don't be humble. You're not that great.

- Golda Meir