Hi Charlie!
Although I have grown over the past few years to fully agree with LJ on
this subject, I can also understand the need for metrics to have something
to go by to know if our performance is on-par or not.
Sadly, measurements in the LOC style no longer give a true picture of
actual
Quantity != Quality
--
Danny Kellett
dkell...@javasystemsolutions.com
On Thu, Jun 5, 2014, at 09:31 AM, Theo Fondse wrote:
**
Hi Charlie!
Although I have grown over the past few years to fully agree with LJ on
this subject, I can also understand the need for metrics to have
something to
. Fast, Accurate, Cheap Pick two..
- Matt Black
On Thu, Jun 5, 2014 at 10:55 AM, Danny Kellett
dkell...@javasystemsolutions.com wrote:
**
Quantity != Quality
--
Danny Kellett
dkell...@javasystemsolutions.com
On Thu, Jun 5, 2014, at 09:31 AM, Theo Fondse wrote:
**
Hi
: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Danny Kellett
Sent: Thursday, June 5, 2014 4:55 AM
To: arslist@ARSLIST.ORG
Subject: Re: Remedy Developer Performance Metrics
**
Quantity != Quality
--
Danny Kellett
dkell...@javasystemsolutions.com
The thought of trying to measure something as fungible as development --
given that there is usually more than nine way to skin a cat in Remedy --
tends to make me believe the idea stems from a manager with far too much
time on their hands.
And as far as measuring development, I would think you
A good start for metrics could be the number of bugs/issues raised against a
development effort and the number of occurrences of the same behavior over a
period of time.
Regards,
Roney Samuel Varghese.
Sent from my iPhone
On Jun 5, 2014, at 8:50 AM, JD Hood hood...@gmail.com wrote:
**
Totally with you, JD!
Rick
On Thu, Jun 5, 2014 at 6:50 AM, JD Hood hood...@gmail.com wrote:
**
The thought of trying to measure something as fungible as development --
given that there is usually more than nine way to skin a cat in Remedy --
tends to make me believe the idea stems from a
Hmmm... If the bugs could be traced to a given developers competency rather
than due to conflicting or poor reqs and/or otherwise unintended
consequences of the reqs, you are likely on to something...
But shouldn't we already be capturing something along those lines from the
root causes
It’s been a really long time where I worked in a shop where you can assume that
1) you have completed requirements, 2) that you can do only development work,
and 3) it’s entirely a custom application. This seems to be fairly rare in our
world of ITSM. I can say that with out of the box
Hi,
I once got the assignment to add some functionality the ITSM notification
system.
I could probably have hammered away right away, adding a bunch of field and
loads of FLTR/ACTL/ESCL to do this. Maintaining that solution would have been
a nightmare.
Instead I sat staring at the existing
04, 2014 8:43 AM
To: arslist@ARSLIST.ORG
Subject: Re: Remedy Developer Performance Metrics
Hi,
I once got the assignment to add some functionality the ITSM notification
system.
I could probably have hammered away right away, adding a bunch of field and
loads of FLTR/ACTL/ESCL to do
Lotridge
Sent: Tuesday, June 03, 2014 9:01 PM
To: arslist@ARSLIST.ORG
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
Charlie,
I have a long standing hatred of performance metrics, that I won't go into
the background for here, but I'll attempt to answer the basis of your
question.
Where I work currently, we went through an 'Agile transformation' a few
years back. We all went through training on how to develop
Hi all,
Thanks for all your responses. And, while I didn't get quite what I was
looking for, it's certainly my own fault for not starting with the more
narrow question I eventually posed. And even that I should have qualified
by stating assuming perfectly efficient workflow.
I fully agree with
discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Charlie Lotridge
Sent: Wednesday, June 4, 2014 10:42 AM
To: arslist@ARSLIST.ORG
Subject: Re: Remedy Developer Performance Metrics
**
Hi all,
Thanks for all your responses. And, while I didn't get quite what I was
looking
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
If what you are looking for is the old Lines of Code (LOC) measure used
in the COCOMO Model and others, then I have always equated an Action
Request System (ARS) object (Active Links, Active Link Guides, Filters,
Filter Guides, Menus and Escalations - Not Forms) to 50 lines of code. I
believe this
My opinion is that 'performance metrics suck and don't work the way they
are intended'. There has been healthy debate over the years regarding
exactly that subject, and every time it's happened, either on the list or
otherwise, it ends up being that no one 'metric' can accurately say that
this
LJ says 'performance metrics suck and don't work the way they are
intended'. So, do you feel strongly about this? Yikes! ;)
Really, though, while I didn't participate or even see any of those prior
conversations about this subject, a couple points occur to me...
First, while you're of course
Charlie, I don't mean this in a RTFM kind of way, but you would do
yourself a service by searching for and reading the previous threads on the
topic. I think they would answer your questions.
Rick
On Jun 3, 2014 4:03 PM, Charlie Lotridge lotri...@mcs-sf.com wrote:
**
LJ says 'performance
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
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
...@earthlink.net310.829.5552
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Charlie Lotridge
Sent: Tuesday, June 03, 2014 6:01 PM
To: arslist@ARSLIST.ORG
Subject: Re: Remedy Developer Performance Metrics
**
Dave,
Ok, fair enough. And I agree
23 matches
Mail list logo
