http://blogs.atlassian.com/2013/11/enterprise-agility-maturity-matrix/
The Enterprise Agility Maturity Matrix can be used to set transformation goals, monitor progress, and get everybody on the same page regarding Agile including: Agile Coaches, team members, managers, and senior leadership. This tool has also been used in many other creative ways, such as to focus retrospectives and to help people at all levels do a self assessment of their own understanding of Agile so as to encourage self-paced learning and open people up to learning from folks that may have more Agile experience.
The tool is a spreadsheet with a section for describing the organization as a whole and another section which is for describing individual teams. There are a number of Agile indicators for each section and each indicator ranges from a ‘0’ (impeded) to a ‘4’ (ideal). For each cell in the matrix, there is a simple English explanation of what it means to be at that level for that indicator. The goal is to get as many indicators to a ‘2’ (sustainable) as possible. This helps the organization understand when they are over the main hump of adoption so that they don’t stop investing in the adoption too early. If not enough indicators get to the sustainable level, the organization will likely backslide to its old ways.
This Enterprise Agility Maturity Matrix was initially developed by a large group of Eliassen Agile Coaches that have had experience with Enterprise Agile Transformations at a wide range of organizations. Over the past six months it has been more widely disseminated via seminars and webinars, and has been refined based on the input of people who have downloaded it and provided feedback. We are now making it even more widely available via this blog, and look forward to your feedback. We will continue to provide additional information on how to best use this tool in future blog postings.
Category |
In transition (1) |
Sustainable (2) |
Agile (3) |
|
Comments |
Owner |
2-Impediments |
|
Raising impediments is becoming routine and there is a high degree of comfort in doing it. Impediments are usually resolved. Root cause analysis is sometimes performed and there is a growing recognition of its value. |
Impediment raising and resolution are a cultural norm. Individual and team impediments that can be addressed at those levels are addressed. Root cause analysis is frequently performed and acted on. |
Current impediments can rise from team but haven’t track in high degree. Root cause analysis is not frequently performed. |
Scrum master |
|
2- Definition of ready |
|
There is a fairly good definition of ready which resulted from the collaboration between multiple members of the team. Definition of ready includes existence of acceptance criteria |
There is a strong, clear, comprehensive (yet simple) definition of ready which resulted from the collaboration of most of the members, agreement and input from all, and it is publically posted |
Definition of Ready didn’t fully understand by PO side and team always urge for AC. |
PPO: |
|
2- Story size |
|
It is apparent that story size is having an adverse effect on the process |
Team has a rule of thumb encouraging small stories |
Story still not small enough for team and hope can split more |
||
1-Progress tracking |
Progress is tracked and known using burnup, burndown, CFD or similar method and sometimes used to influence behavior |
Progress is tracked and frequently influences the behavior of the team |
Progress information usually influences the behavior of the team |
Progress is tracked by CFD, but team didn’t use to influence team behavior usually. |
Team |
|
1-Test automation |
30%+ code coverage via test automation and plans are in place to increase this level |
50%+ code coverage for all new user stories via test automation |
50%+ code coverage via test automation |
Test automation can’t follow the step of implements; automation script should be part of code release from Team and making sure multiple members can work on one story. |
Team |
|
ATTD should adopt to make sure Acceptances Test ready after AC is clear and mark is as a basic testing entrance for UAT. |
Team |
|||||
1-Refactoring |
Some understanding of single responsibility principle (SRP) and open/closed principle. Some amount of refactoring done as needed when implementing stories. |
Refactoring around SRP and O/C principle. Doing the appropriate amount of refactoring with most user stories |
Deep understanding of refactoring. True refactoring is a cultural norm. |
Some amount of Refactoring done but Team didn’t how to appropriately abstract our design, which requires in-depth knowledge of OO design, pattern and refactor technique, etc. Need Coding Dojo as a platform to improve personal skill. |
Team |
相关推荐
•AMM(敏捷成熟度模型) 全称Agile Maturity Model,是一套用来评估软件开发团队或者整个开发组织的当前敏捷状态和将来的目标状态的框架,评估的结果用来帮助团队识别改善点。 •可以评估一个IT组织的敏捷程度,其...
agile 9.3.6英文文档 Oracle's Agile PLM documentation set includes Adobe® Acrobat PDF files. The Oracle Technology Network (OTN) Web site ...
Agile has revolutionized the way teams approach software development, but with dozens of agile methodologies to choose from, the decision to "go agile" can be tricky. This practical book helps you ...
Agile Testing A Practical Guide for Testers and Agile Teams 英文epub 本资源转载自网络,如有侵权,请联系上传者或csdn删除
Wi-Fi CERTIFIED Agile Multiband是 Wi-Fi Alliance 的一项认证计划,其目的是使 Wi-Fi 网络资源能够得到更好的利用。Wi-Fi Agile Multiband设备支持动态交换有关网络环境的信息,支持以智能化方式将客户端设备引导...
Foster team development: co-location, self-organization, cross-functional roles, and how to bring the customer aboard Facilitate technical tasks and processes: testing, refactoring, continuous ...
Learn the agile philosophy of lean processes, incremental delivery, deep client participation, decentralized authority, and just-in-time planning to bring speed, creativity, empowerment and increased ...
Introduction in agile process
Agile Crystal Methology
Agile Software Development
Agile Retrospectives
Agile.net Code Protection - Powerful .NET Code Protection & Obfuscation Solution Agile.NET code protection solution offers better protection for your .NET code by providing a protection that goes ...
The goal of the book is to teach your agile team which metrics it can use to objectively measure performance. You'll learn what data really counts, along with where to find it, how to get it, and how...
Best practices for managing projects in agile environments—now updated with new techniques for larger projects Today, the pace of project management moves faster. Project management needs to ...
Practices Of An Agile Developer
JIRA Agile is a plugin that adds agile project management to any JIRA project. It allows you to visualize your existing process and stimulate incremental improvement. JIRA Agile brings the power of ...
Agile Java Example Code
The Agile movement provides real, actionable answers to the question that keeps many company leaders awake at night: How do we stay successful in a fast-changing and unpredictable world? Agile has ...
Agile role 说明,对于理解agile模式有帮助
Agile training What is Agile? Agile Manifesto Principles behind Agile Manifesto Agile Methods Scrum and XP Agile Testing