Metrics are a challenge to make your metric look good.

Specifications are how a boss expresses his/her misconception of the mis-understanding the committee has of the need of the worker.

Problem solving takes understanding of the real need, resource limitations, an ability to think outside of the box, apply the KISS method and take into account the human factor.

Pay a programmer by LOC and you will get lots of LOC. Can you imagine paying a carpenter to build your house by the number of nails he uses?

Payment/measurement needs to be based upon ROI. If my solution saves a clerk 15 minutes a day ($10 per hour/4 * 5 days per week * 50 weeks) or $625 per year. my solution better not cost more than $1000 or about a year and a half for payback.

The hardest part of a justification is when there is a substantial framework/infrastructure investment required. Payback periods become longer, and future gains based upon that investment need to be analyzed.

Why all the meandering? Because we are all paid for the benefit we provide to our customers/employers. Learn to express it in a way that any business person can understand and you will work on more extensive projects and provide more value as well as reap greater benefits.

Unless you want them to do all the thinking, and try to measure your performance by some number marginaly related to what you do.

I am now stepping down from the soap box.

Enjoy!
John

In reply to Re: (OT) Proving Productivity? by johndageek
in thread (OT) Proving Productivity? by Ovid

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.