Nevermind that we spend more time conforming to arbitrary standards than we do developing money-making software.
If you can quantify this, and then translate it into dollars lost versus dollars saved, you'd have a case to bring to management to at least reduce the frequency of changes if not reduce the number of changes altogether.
Example:
- how many minutes per day do you spend making changes to conform to standards?
- how many minutes are spent by the committee reviewing and changing the standards?
- how many people are in the committee?
- measure these items over the course of one month.
- compute the number of hours
- compute the amount of money spent by multiplying the hours by the average hourly wage (you'll have to figure this out yourself)
- multiply this number by 12 to get the yearly estimated cost
here's the kicker, ask them how much of this money being spent is benefiting the customer!
HTH
--
hiseldl
What time is it? It's Camel Time!
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
