Project Management

Please login or join to subscribe to this thread

Agile maturity

linkedin twitter facebook  
avatar
Divya Gowda Malaysia
In an Agile assessment, Is it possible to have different Agile maturity levels defined for Enterprise and associated Teams. Meaning, can an Enterprise level maturity matrix indicate 5 levels of maturity, and team level maturity matrix choose 4 levels of maturity ? I'd prefer alignment between the two but I also want to understand if that's ALWAYS necessary. esp when the two assessments measure different aspects.
Sort By:
avatar
Keith Novak Tukwila, Wa, United States
An enterprise, like any system, is much more than the sum of the parts. While you could come up with a way to combine the maturity levels of each contributing team to develop an enterprise level score, that is not a measure of the whole organization. When evaluating any system performance, there are 2 prime ways to do that. One is bottoms-up, and the other top-down:

In bottoms-up evaluations you can look at the maturity level of each piece and combine them to represent a larger system. The whole nature of systems however, is that it is the interfaces between all the pieces that make the whole, larger than the sum of the parts. Interactions between how things work make all the difference.

How the interactions between functions within enterprises work, requires a top-down view. It is extremely difficult to evaluate the performance of all the pieces in any system and evaluate the system performance without looking at the interactions/interfaces.

Consider if your director asked everyone to think outside of the box, and all the groups returned with ground breaking ideas, but the director was still too conservative to follow any of those ideas. The innovative nature of the teams are not reflected by the director, and one shouldn't be judged by the other.
avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
Divya -

Depends on what the maturity model is based on. If it is focused on objective value/outcome-based metrics, then you should be able to compare apples-to-apples between teams at an enterprise level.

That may require individual teams to translate or map their metrics to those at the enterprise level.

The danger is when the maturity model focuses on the "how" and draws conclusions based on that as that tends to ignore the principle that context counts...

Kiron

Please login or join to reply

Content ID:
ADVERTISEMENTS

"I never forget a face, but in your case I'll make an exception."

- Groucho Marx

ADVERTISEMENT

Sponsors