Re: How Esc to Dev and Enhancement incidents are handled
Thank you "aa4" for the carefully crafted response.
aa4 said:
These reports then go into a queue which is reviewed and prioritized at the discretion of our Development department and then assigned accordingly.
First priority is given to critical issues that result in loss of data and/or impediment of critical work. Next, attention is given to other issues that affect most users but are less critical and last but not least attention is given to other less critical issues.
So we have at least . . . First, Next and Last. Or, High, Medium and Low. According to Greg's "80-20" rule, this sounds like:
First ( High ) . . . . 80% "Time proirity" > > "Impediment of Critical Work".
Next ( Medium ). . 15% > > "Workarounds OK for now"
Last ( Low ). . . . . 4% > > "Do you want that with cheese ?"
but all of them will at least be reviewed.
And 1% get "Trash-Canned".
I guess the percentages might be "off", but we get the picture. Sounds REALLY GOOD.
I forgot to mention that we have changed the process so now anytime an incident is updated, a notification e-mail is sent to the account owner with a link back to the original incident.
IF, an Incident is UPDATED, when it is Prioritized by Development, THEN Progress has been made.
IF a Priority Level is included when an Update Notification is sent to the Incident Owner, THEN many CLOUDS have been lifted from this issue.
Thanks > Barry