General discussion

  • Creator
    Topic
  • #2123459

    developer pool

    Locked

    by sender ·

    I am the IT Head of a small (120 staff) non-IT company. One day, our CEO asked me why I always ask for additional headcount for support when we have new system launched. He suggest me not to divide the IT department (25 IT staff) into team, but group them all as a pool so that the pool can support everything. How will you handle this situation?

All Comments

  • Author
    Replies
    • #3555047

      developer pool

      by fossil ·

      In reply to developer pool

      (This is in two parts — not enough room) On the surface, the CEO has what seems like a reasonable idea. Unfortunately, it isn’t that simple. He needs to understand that each system that is supported is somewhat like an automobile. One good mechanic can work on all types. But, is that the best way? It takes time to learn the ins & out of each automobile — “regular” engines, rotary engines, deisel engines, etc. The emissions systems are different, and so on. To an observer, it might seemlike “a car is a car”. A mechanic knows differently. Software has many similarities to cars in that regard. Almost any developer should be able to work on simple software — reports, etc. When it gets more complicated, additional expertise is necessary. Knowledge on not only the technical side — the language(s), the database system(s), communications protocols, intermodule communciations, etc., but also the business logic embedded within the software. Someone working on the accounting software, will eventually, learn a lot about accounts, and how they interrelate. The database guru won’t, but does instead have a different set of skills. The CEO needs to be educated into understanding that just as cars are different, so is software. He’s not totally off base though. It does make sense to rotate staff amongst the work for lots of reasons. But there is a cost. If Mary has 5 years on the accounting software and Bob starts handling it, Bob won’t get things done as quickly, and will probably need some of Mary’s time also. So two staff, with 5 years in each of their own areas that swap roles, would require more than the 200% to get the same work done as they did before the swap. If the CEO is willing to invest in that (youhave to come up with the plan/cost) then, yes — he can get to the “pool”, but cross training staff with more than one specialty is probably a more cost effective way to go.

      • #3555046

        developer pool

        by fossil ·

        In reply to developer pool

        (part 2)
        One inexspenive way it at dept. meetings have a presentation on exisitng systems — one per mtg. Have the ‘expert” and a novice work together in preparing and giving the presentation. Have some upper mgmt sit in too. It ends up a win for all involved (I hate the lingo, but bosses love it). Good luck.

      • #3424279

        developer pool

        by sender ·

        In reply to developer pool

        The question was auto-closed by TechRepublic

    • #3553917

      developer pool

      by realgem ·

      In reply to developer pool

      Pools can work, but it would not be good to go to extremes.

      If each person in the pool has to support many products, then they will not be as good with each product has they would if they were only supporting one or two.

      Some products, like networks, require constant support and monitoring. It would be very confusing to have many people doing this. They would be stepping all over each other.

      The last point, and this is the most important one, if you are launching and supporting a newproduct, there will be MORE work to do. I don’t know if there would be enough to justify hiring new staff, but eventually you would have to do this.

      I would probably be a good idea to form teams, and have each team specialize in one area: networks, desktop tools, programming, servers, etc.

      • #3424280

        developer pool

        by sender ·

        In reply to developer pool

        The question was auto-closed by TechRepublic

    • #3565785

      developer pool

      by cilik001 ·

      In reply to developer pool

      One key factor I believe we need to know is how many systems we are talking of.
      Also , are we developing in-house or are the systems developed by some third party ? – Will your staff therefore provide first level of support ?

      I believe both factors help in opting between pooling and teaming. The good thing about teams is that staff may specialise in the systems and therefore may provide more efficient support. This is harder with pooling- however this again depends upon the degree of support which your staff intend to provide. That is why I believe that we need to know some further info to be able to qualify the options.

      • #3424281

        developer pool

        by sender ·

        In reply to developer pool

        The question was auto-closed by TechRepublic

    • #3564681

      developer pool

      by wayne m. ·

      In reply to developer pool

      If you have a good relationship with the CEO, ask him if he would like to join the IT department pool. Use this as an example how, like business, IT has different skill and knowledge areas and no one can be an expert in all of them.

      On the otherhand, if 25 out of 120 people are IT support staff and you continue to ask for more staff for every new system, perhaps the CEO has a point and your staff may be getting too specialized.

      • #3424282

        developer pool

        by sender ·

        In reply to developer pool

        The question was auto-closed by TechRepublic

    • #3571240

      developer pool

      by shri21 ·

      In reply to developer pool

      I find ratio of IT-staff to total-staff is somewhat high for non-IT company. Here is what you can do:

      1. Frist develop short but job descriptions of each IT staff.

      2. Then list all applications and work/functions (like operations, developer, support, Lead) with who is doing it.
      E.g.
      Developer Installer Operator … .

      Apps-1 …(initials-with-skills-C-COBOL)…

      Apps-2 ………as above ……………..

      3. Now analyze the two lists produced above. You could find ways to re-organize the sections in IT. E.g. It may be good to combine Operations functions of related Applications or it could be easy to combine related Applications. Keep in mind individual preferances and try to accomodate them.

      4. Based on decisions in step 3 – cross train wherever required. I think it is always good to have more than couple of people trained and experienced in critical areas if the business. Keep rotating IT staff till staff has real hands on areas they are supposed to know.

      Hope this will help you in your problem. Let me know the results if you can.

      • #3424272

        developer pool

        by sender ·

        In reply to developer pool

        The question was auto-closed by TechRepublic

    • #3448938

      developer pool

      by windrider ·

      In reply to developer pool

      Two things strike me as unusual.

      1 – The CEO is telling you how to do your job. If you are up to it you should be leading the IT show, be way ahead of the CEO, and telling him what you want to do to help the business.

      2 – Not many business models support an IT labour spend that is 20-30 % of total. More common ranges are 4-12%.

      Suggest you hire a strategic consultant, do a little benchmarking, and develop an IT plan that makes the most sense for the business.

      • #3424283

        developer pool

        by sender ·

        In reply to developer pool

        The question was auto-closed by TechRepublic

    • #3449622

      developer pool

      by shanghai sam ·

      In reply to developer pool

      As expressed in several answers already, there seems some merit to the CEO’s position given the fairly high ration of IT staff to overall staff.
      I would be inclined to examine the reasons I needed to ask for additional support for new systems — and would ask myself if IT involvement in new projects is early enough to influence platform and technology choice, so that projects’ technologies align as much as appropriate with existing company platforms and technologies. This reduces width of skills needed across your IT staff.

      In addition, when considering dividing existing staff into teams, consider the advice of Bob Lewis in chapter 2 of his “IS Survival Guide” (SAMS Publishing). He speaks of allocating the three types of IT resourcesin every company — operational (keeping things running), tactical (projects to improve company’s compettiive position) and strategic (projects which move the company into the future) — via percentages that are guided by the company executive steering committee. Since the steering committee sets project priorities across the company, base your three types of staff allocations on this.

      For example working with the executive committe might result in a 40/20/40% split: 40% of resources to keep things running; 20% to tactical projects, and 40% to strategic projects.

      The 40% to operational and the 40% to strategic should not exceeed these limits. Your tactical 20% though is your advantage. That is because the business sponsors for these tactical projects can estimate a return on investment (via reduced production costs or improved company margin). Thus money is made via your tactical projects — and a project that makes money is a project that the company can borrow on. When you indicate to your CEO that your taactical IT project makes the company x%, you have provided the funding for any temporary additional staff for that tactical project. Thus you can b

    • #3424271

      developer pool

      by sender ·

      In reply to developer pool

      This question was auto closed due to inactivity

Viewing 7 reply threads