I am managing a large software implementation and we are using the BAI (Build, Acquire, and Implement) domain. I need advice on how to set up performance metrics that track both the quality of the build and the speed of implementation. Most our current KPIs only focus on the budget, but we are seeing a lot of post-implementation defects. Any suggestions?
3 answers
For the BAI domain, specifically BAI03 (Manage Identification and Build) and BAI07 (Manage Change Acceptance and Transitioning), you should implement "Defect Density" and "Post-Implementation Review (PIR) Success Rate." Instead of just tracking the budget, monitor the "percentage of business requirements met in the first release." This forces the team to focus on quality. Also, track the "time between build completion and production deployment" to measure implementation speed. This balanced approach ensures that speed doesn't compromise the integrity of the software.
Have you considered integrating your Agile velocity metrics into the COBIT performance framework, or are you keeping your project management reporting completely separate from the technical KPIs?
You need to focus on "BAI06: Manage Changes." High defect rates often stem from poor change control. Track the "number of emergency changes" as a key quality metric.
Definitely. Jennifer is right; emergency changes are a huge red flag. Reducing them usually leads to a much more stable production environment and higher stakeholder trust.
Integrating the two is vital. If you track "Sprint Burn-down" alongside "BAI Process Capability," you get a much clearer picture of project health. I suggest mapping Agile 'Definition of Done' to the COBIT 'Process Outcomes.' This ensures that the technical quality standards expected by the governance framework are being met within every development cycle without creating extra manual reporting overhead for the devs.