Loading ...
Sorry, an error occurred while loading the content.

154065Re: [XP] Cost of Process Changes?

Expand Messages
  • Tim Ottinger
    Jun 9, 2010
      Cost: your sanity, 5% of the team at least, and management upset.

      Less joking:

      If you actually want to prevent a change, measure it by the day, hour, or week.
      If you want it to succeed, then measure it by the quarter or year.

      After two years, we have measurable improvements (huge decrease in known errors, faster release of small new features, shorter release test cycles, fewer regressions, fewer broken builds per month, decrease in code size, increase in test count and test coverage, etc.

      If you measured two or three months in, all of the good measures would be down and all the bad ones up.

      Tim Ottinger
    • Show all 8 messages in this topic