Re: Work to the risk was Re: Inspections Was: RE: [AM] ANN: Mashing Deadly Myt
"Scott E. Preece" <[email protected]> Wed, 25 Feb 2004 10:40:04 -0600 (CST)
| Newsgroups | gmane.comp.programming.modeling.agile |
|---|---|
| Message-ID | <[email protected]> |
| From: "J. B. Rainsberger" <[email protected]> | | 1. Continually overestimating the ROI on inspections, usually by | overestimating the cost of defects /or/ underestimating the defect | removal capability of the other XP practices. | | 2. Paying lip service to inspections with a low "fix rate," that is, | using inspections to uncover problems but not taking the time to | actually fix them. This is just like testing in the last three weeks of | the project, then management saying, "We can't afford to fix that problem." --- I completely agree. An organization should have a good picture of what it costs to fix defects at each phase of development, and when defects are reported, they should include an estimate of the cost of fixing the specific problem in deciding whether/when to fix it. The organization should also have a good understanding of the potential costs of shipped defects - how much it would cost to re-release and what the potential liability issues are for different kinds of product failures. It's important to understand that we are a litigious society. It is COMPLETELY possible to be sued for large amounts of money if you make alarm clocks and somebody suffers a loss as a result of your alarm clock failing to go off when it was supposed to. Typical inspection process definitions require that all reported defects be tracked to resolution; however, resolution can include deferral to a subsequent release or deciding that a particular defect isn't worth fixing. We typically require that operational defects (ones that would interfere with use of the product) must be fixed before ship, but there is a review step that can allow exceptions, if the business agrees. --- | | I have to see inspections be used appropriately before I can believe | their value. I haven't had that experience yet. --- That's fair. --- | Pardon me, and no hard feelings. --- That's OK, I overheat sometimes, too. scott -- scott preece motorola urbana design center (il67), 1800 s. oak st., champaign, il 61820 e-mail: [email protected] fax: 217-384-8550 phone: 217-384-8589 cell: 217-433-6114 pager: [email protected] For more information about AM, visit the Agile Modeling Home Page at www.agilemodeling.com --^---------------------------------------------------------------- This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrKDA.bWnbtk.Z2NtYS1h Or send an email to: [email protected] TOPICA - Start your own email discussion group. FREE! http://www.topica.com/partner/tag02/create/index2.html --^----------------------------------------------------------------