Blog Entry
979
Every week the global GroupWise support team attends a Top Issues meeting (virtually for some of course) to go over the bugs reported in the previous 7 days. Part of the meeting, hinted at by the name, is to define the Top Issues. This is the part where we all sit and look at each other blankly and normally end up making something up. Now don't worry, it doesn't affect you in any way but it's what gets written in the Top Issues report and put on our internal Meeting Minutes website.
The main focus of the meeting is to prioritize the issues and decide where they should be fixed so it's not that we are missing the point of the meeting - noting down the Top Issues is designed to give our Field Support engineers an idea of the most intrusive and common issues that our customers are seeing. The problem we face is that very few of the issues that we get in are common - obviously every now and again there is a contender, I am not denying that - but on a week to week basis they are very few and far between. So how can we decide which one of them is a top issue? Of course, having pointed this out to our managers, we get some puzzled looks because the other teams seem to have no problem identifying their top issues.
So I guess I wonder if the same view is held out there? GroupWise, being one of Novell's only user facing products draws a lot more attention that most others, however, are the issues normally widespread or piecemeal? Are there other products where, if one person has an issue everyone has an issue (like high utilization in eDirectory)?
Related Articles
User Comments

If the issues are too
Submitted by John Yorke (not verified) on 10 May 2007 - 12:45pm.
If the issues are too granular to put in a top ten then maybe they can be classified into larger groups. For example "items which could be resolved with a tuning wizard", "items which could be resolved with install process improvements", "items which could be resolved with a setup analysis tool with diagnostics", etc. Even though issues might be all different in symptom and resolution, perhaps there are classifications that are a little more general but not too generalized so that the classification can add value.
- Login to post comments

Not a bad idea John - there
Submitted by Alex Evans (not verified) on 10 May 2007 - 2:21pm.
Not a bad idea John - there is another report that Support delivers back to Development where we do bundle issues together like this, and categorize them under a more general heading. The Top Issues meeting/list is normally to identify particular bugs that are causing lots of calls or impact large portions of a user base - which is where we struggle. Even if we did bundle them together on a weekly basis we probably couldn't come up with a list that was targeted at a particular set of related issues - only when collated over a couple of months or more would we get such a list.
- Login to post comments

Do you know of any add-on to
Submitted by Rich (not verified) on 18 May 2007 - 1:54pm.
Do you know of any add-on to Groupwise 6.5 that would allow me to check off or note when a phone message has been returned?
- Login to post comments





3