Timeline for Handling internal IT issues
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 4, 2014 at 16:22 | vote | accept | woz | ||
| Mar 4, 2014 at 7:48 | comment | added | Jeff Langemeier | @mattnz Yes, convince, but it's an easy sell if you can show them dollar signs. A shop where the devs are the internal IT staff is probably fairly small so there isn't a lot of bean counters in the way. A dedicated IT guy is a headcount increase of 1 per 40 hours worth of load that it takes off the devs, that's 40 more dev hours per week (extra man-month per month), this should directly relate to increased productivity, and therefore faster widget output. | |
| Mar 3, 2014 at 23:09 | comment | added | mattnz | In theory your answer is good, except "should" "easy" and "convince appear in the same sentence. This is most like the problem - typically management don't understand the difference in roles, and you are proposing a head count increase as if its a wave of a magic wand, when something they won't do lightly. My guess, it won't happen..... | |
| Mar 3, 2014 at 19:29 | history | edited | Jeff Langemeier | CC BY-SA 3.0 | added 267 characters in body |
| Mar 3, 2014 at 19:24 | history | answered | Jeff Langemeier | CC BY-SA 3.0 |