Scribd
Upload
383 views1 page

Agile Maturity Guide

Uploaded by

pnorberto
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
383 views1 page

Agile Maturity Guide

Uploaded by

pnorberto
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

AGILE MATURITY LEVELS GUIDE

Maturity Level IT Project/Initiative-Specific Business Agility

Pre-Crawl -
-
Little or no use of automated tools to test, deliver, and maintain software code
Data migrations are manual and undocumented
-
-
Siloed operations
Command and control management
- Initiatives are poorly planned
and/or ad-hoc
- Infrequent releases - No business architecture - Mistakes are punished
- No real tracking of defects - No/few documented processes -Keeping everyone busy is important
- Business and IT are “at odds” - Success based on individual performance
Or Backwards - Massive and formal requirements documents - No measurements

- Agile frameworks are learned and one or more are implemented


Crawl - Requirements documented - Work has a quantifiable value
- Some automation of testing/development/integration - Value is used to justify, prioritize, and fund work
- Data migrations are manual and undocumented - Work is transparent and there is a shared understanding of it
- Some management of solution requirements - Some metrics are tracked
- Infrequent releases
Repeatable - Tracking of defects in place
- Unacceptable level of defects

Walk - Agile principles are applied - Agile principles and values are embraced at the business level
- Agile frameworks are being adjusted to the organization - Strategic goals have incremental checkpoints to ensure that all work aligns with the
- Consistent automated build and testing organizational goals
- Good management of dependencies and risks - Management is moving to servant-leadership
- Reusability of scripts, tests, and tools
Consistency

- Value-based metrics are built, measured, and acted upon


Run - Release and rollback processes tested
- All business outcomes have relative targets and regular measures (including
non-financial measures)
- Deployment managed - Work, projects, and/or products are started up, pivoted, or stopped easily
- Application monitored and proactively managed
- Non-functional requirements defined and measured
Manage by - Databases are monitored and optimized

Measured Value

- Frequent collaboration between teams to discuss integrations and automation effectiveness


Fly
- Adaptive funding models are used to allocate funds against value streams
- Fast feedback loops (defects found and fixed quickly)
- Governance is aligned to value delivery
- Experimentation and innovation encouraged
- A systems thinking approach to the business is embraced
- Full automation and virtualization used where applicable
- Work, systems, and value streams are visualized and managed
- DevOps environment
- Risks managed effectively
Optimized based on - Production roadblocks are rare
Value + Innovation - Loose coupling of design and architecture

© 2021 Netmind SL

You might also like