4 replies
by timwalsh
I'm afraid you won't find any common or standard ration. Different organizations have different needs. These needs are based on such things as complexity of systems ad software, complexity of network environment, level of user education on systemsans software being used, whether or not the software /hardware being supported is proprietary, corporate politics, corporate culture, budget, etc.
Therefore, the best answer you are likely to get is "whatever works for your organization."
by thechas
If you take a look through both the discussion center, and the Q&A forum, you will find numerous peers looking for the same question to be answered.
As Tim said in his post, there is no 1 correct answer, standard, or formula.
In the downloads section, there is a spreadsheet that can be used as a staffing guide.
Bassically, you need to establish a set of metrics to measure both the effectiveness of your staff, and the quality of support provided.
If the staff has excessive idle time,then you are overstaffed.
If response times are too long, or quality of support is falling, then you need to add staff.
Chas
by j.bird
Tim/Chas, you're both right of course. Question isn't defined appropriately,too many variables, etc. But in IT we have to work with these imponderables. The time-line on your projects, even if you're repeating a project is still at best,a guess.
Iwas looking for a general indication only.
by dkerta
The calculation is not too difficult if you alredy have system portfolio in your hand. Firts, start with critical system application, develop SLA with the users of how long system recovery need in case of failure, calculate number of staff to cover the SLA, with a clear escalation procedure.
That's just an example.
This discussion is closed to new replies.
Trending IT Employment posts
Sort by Trending