- 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.7 Consensus within the Agile Community
The agile community can be both opinionated and very vocal. It can also be difficult to gain consensus. You need to expect that there will always be a diversity of views and opinions expressed in the agile community. Sometimes, views are expressed in rather emphatic terms. In fact, it is the great irony that some agile practitioners are the least agile people I have ever worked with, insisting that agility can be practiced in only one particular way. My view is to enjoy the plurality of opinions, looking for consensus when I can find it and also understand that sometimes experienced practitioners will have differing points of view. This is especially true when confronting some of the more thorny issues in understanding agility. One of these considerations is what agile process maturity is not.