>From seeing all the responses, I won't echo their thoughts or go into numbers such as # of objects created per day and all that. To look at it from a management point of view, I would try to measure the performance of Remedy devs the same as I would manage any other member of the IT staff. Are they working Incidents, Problems, Changes? Are they responsible for creating knowledge articles? I would look at the following metrics: 1. # of Successful vs. Failed changes where they are the Implementer 2. # of Resolved Incidents per time period 3. # of Re-opened Incidents per time period 4. # of changes implemented per time period 5. # of workarounds/ problem solutions found per time period 6. # of knowledge articles submitted 7. # of incidents that were not escalated Of course, I'm assuming that anything they are working on is based off of a request whether it be Incident/Change/Problem.
Also, you can do a "360" evaluation where you survey their peers to see how they are doing (Many HR departments implement these types of evals these days). So while I'm sure this doesn't answer your question, I hope it offers a practical way of evaluating performance for the poor SOB that is getting an evaluation :) On Tue, Jun 3, 2014 at 5:46 PM, Charlie Lotridge <[email protected]> wrote: > ** > Hi all, > > I'm curious...what are your opinions about what might be useful metrics to > use to judge the performance of Remedy developers? To narrow the > conversation a bit, let's just talk about during the creation of a new > custom application, or custom module to an existing application. In other > words for code generation. > > So for example, you might tell me that a good developer can create at > least 50 logic objects (active links/filters/escalations) in a day. Or > create & format one form/day. > > What are you opinions? > > Thanks, > Charlie > _ARSlist: "Where the Answers Are" and have been for 20 years_ -- *Tauf Chowdhury* _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
