- 4.1 Goals of Agile Process Maturity
- 4.2 Why Is Agile Process Improvement Important?
- 4.3 Where Do I Start?
- 4.4 Understanding Agile Process Maturity
- 4.5 Applying the Principles
- 4.6 Recognition by the Agile Community
- 4.7 Consensus within the Agile Community
- 4.8 What Agile Process Maturity Is Not
- 4.9 What Does an Immature Agile Process Look Like?
- 4.10 Problems with Agile
- 4.11 Waterfall Pitfalls
- 4.12 The Items on the Right
- 4.13 Agile Coexisting with Non-Agile
- 4.14 IT Governance
- 4.15 ALM and the Agile Principles
- 4.16 Agile as a Repeatable Process
- 4.17 Deming and Quality Management
- 4.18 Agile Maturity in the Enterprise
- 4.19 Continuous Process Improvement
- 4.20 Measuring the ALM
- 4.21 Vendor Management
- 4.22 Hardware Development
- 4.23 Conclusion
4.6 Recognition by the Agile Community
Agile development is part of a large ecosystem with an active and involved community. Mature agile processes are aligned with agile principles and are recognized by the agile community. Much of my work involves taking innovative and even risky approaches when I customize software methodology to meet the unique needs of often complex organizations. Although I always maintain confidentiality, I find it effective to write and publish articles that describe my approach to DevOps and agile process maturity. Sometimes, my views are well accepted by the agile community, and other times the reaction can be quite significant. I actually use my esteemed colleagues in the agile community as a feedback loop to continuously improve my own process methodologies.
Recognition within the agile community is a worthy goal. However, gaining consensus may be much more difficult to achieve.