To me, Charlie seems like a PM type who, by his own admission doesn't understand how to measure development in Remedy. That's ok, no one else really can, either, except by results over a long period of time. To people like Charlie, who do an important job that I'm not trying to denigrate, there needs to be a separation between the "What" and the "How". The customer tells us What they need, the PM works with the developers and customer to come up with a combination of scope and schedule that works for them all, but the How needs to be the domain of the developer/architects. When people who don't understand a technology try to insert themselves into it, it slows the process and almost cannot improve the results. Leave engineering to the engineers, and measure the results more than the process.
Rick On Wed, Jun 4, 2014 at 8:10 AM, Jim Coryat (jcoryat) <jcor...@micron.com> wrote: > ** > > Ok, I agree more with LJ than Charlie, but I see both sides. > > > > Personally having been a software engineer for many years. It really > depends on what you are trying to discern. While this is a discrete > discipline, you can measure the overall project progress and estimated > completion timeline to give you a rough approximation of performance. I > have worked with project managers in the past in generating estimates of > effort based on the number of artifacts within a system that will need to > be changed and estimates of effort for each etc. You could roughly derive > a metric from that. However that does not take into effect when > complications arise and do not fit into the paradigm, which will reflect > poorly in the metric. There is no replacement for knowing the subject > matter and being able to communicate with your team on performance. > > > > I can churn out objects by the gross, however the quality delivered may be > another thing. My point is don’t get caught up in the counts as your > measurement, use it as one of several metrics which will give you a more > accurate interpretation. > > > > Jim Coryat > > x34655 > > > > *From:* Charlie Lotridge [mailto:lotri...@mcs-sf.com] > *Sent:* Tuesday, June 03, 2014 7:01 PM > *Subject:* Re: Remedy Developer Performance Metrics > > > > ** > > Dave, > > > > Ok, fair enough. And I agree there are a lot of > qualifications/considerations. > > > > I'm seeing now, though, that I posed too broad (and sensitive) a question. > Let me try a different angle on this, which should be sufficient for my > needs: > > > > On a good day, and if it's all you had to do, about how many workflow > objects (AL's, filters, escalations) can you create (minimum, maximum, and > average)? > > > > For me, if it's very complex workflow, it might be as low as 15-20 objects. > > > > On the other hand, if it's a highly mechanical operation - e.g. I need to > replicate the same On Return active link that perhaps calls a common guide > across all the fields of several forms, so I'm only changing the field id > and doing a "Save As" - it might get up to a few hundred (say one/minute). > But even on my worst day and the most complex workflow it's not going to > be just one object on the low end, and it's never going to be a thousand on > the high end. > > > > So for me, min to max, my answer would be 15 to, say, 400. And, on > average, I'd say it's probably around 30 or so. > > > > So, anyone willing to answer, I'd appreciate the data points. > > > > Thanks, > Charlie > > > > On Tue, Jun 3, 2014 at 4:44 PM, Shellman, David <dave.shell...@te.com> > wrote: > > Charlie, > > Being an AR System admin is not about how many active links or filters or > fields one can put together in a day. Do they work as intended? Are the > permissions right? If they are not working as intended how well does the > individual do to figure out what is not right and correct the problem. Is > it entirely new workflow or is the individual adding to something another > person put together? Or they finding and correcting issues and with > existing workflow. > > If you count workflow objects one could do coding to meet that criteria. > On the other had they could be efficient and combine three actions into one > filter instead of three. > > Finally there is more than one way to create code within the AR System. > One individual could do something one way and another individual > completely different. Both ways meet the design requirements. > > Dave > > > On Jun 3, 2014, at 5:46 PM, "Charlie Lotridge" <lotri...@mcs-sf.com> > 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_ > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > > > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
