- 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.17 Deming and Quality Management
Many of the lessons from Deming are a main focus of the agile ALM, and we will point them out throughout this book. Testing is essential, but there are many other ways to build quality into the agile ALM.
4.17.1 Testing versus Building Quality In
Application testing is a must-have. But quality has to be built in from the very beginning. Code reviews and inspections are among the tools that help ensure quality is built into the product from the very beginning. Ensuring that requirements are well defined is essential for ensuring high-quality systems. The agile ALM provides a comprehensive framework of best practices to help build quality into the product from the very beginning. It is also the best way to help improve productivity.
Technology professionals often find themselves mired in the quagmire of trying to get work done efficiently. The mature agile ALM helps avoid mistakes and rework that is so often the reality of today’s software and systems development effort. One of the most effective practices to improve productivity is rapid iterative development.