> it's one thing to say the structure of the process itself is so byzantine and brittle that schools suck, but it's quite another to say we should remove measur

> it's one thing to say the structure of the process itself is so byzantine and brittle that schools suck, but it's quite another to say we should remove measurable goals as well. What good is it to have measurable goals if you are measuring the wrong thing, or your measurements are corrupt, or there is no effective means of correction if goals are not met? > To continue the programming analogy, as a customer you guys are delivering crap all the time. I pay ten times as much and the crap just gets worse. Now we can sit around and dicker all day long about the process you have for making crap, but one thing we are not going to do is remove the testing at the end that makes it obvious to everybody just how shitty the whole thing is. Keep it in then. Your programming team can learn to game the system, and your management team can quietly lobby to change the metrics so the numbers look better, and you can even bring in a pair of Bobs for a development cycle to shake things up, but none of that actually gets you to working software.