Software Teamwork: Taking Ownership for Success

Chapter Twenty-Three. Progress Revisited

We need to monitor progress on the changes we make to our culture and processes. Although anecdotal evidence can be compelling in some cases, there is no evidence more compelling than quantified data.

This chapter elaborates on the need to take measurements to confirm our progress in what we are trying to achieve, explains that some of the most important measures concern the current costs of dysfunction, and suggests that measurement is for everyone.

Measuring as a Necessary Evil

Few industries view what constitutes a critical practice so narrowly as the software industry. In most software shops, developing and managing requirements is done when we have time. Estimation practice looks a lot like target ...