> From: [email protected] > To: [email protected] > Subject: Re: [LegacyUG] Endnotes > Date: Sat, 15 Feb 2014 10:53:18 -0500 > > Any chance we can agree that you're both right, up to a point? My experience is similar to that outlined by Ward, where problem reports (a.k.a. defect reports) have both a severity and a priority. The fine details will differ from system to system, but in, say, a business environment, one might have, perhaps, four problem report levels. A priority 1 would be a showstopper : for example, something that immediately affects the customer's revenue stream, and would require an emergency fix. A '2' might be severe, but with a workaround that would mean an urgent fix was still required before the next scheduled release, but not otherwise preventing, say, the issue of bills to the customer's customers (always a serious affair). A '3' might be something with a significant impact, but for which a workaround is available and a fix could be held over until the next scheduled software release, and a '4' might be cosmetic or minor, again requiring nothing faster than the next release. Problem reports would then be assigned to the programmer teams with a fix-by date attached and associated with the severity of the problem. The programmer team reacts to the impact on the end user, not the impact on the programmer team. Just for the avoidance of doubt, I'm only making general observations here, not anything about how Millennia Corp operates its problem management system. Alex
Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
