Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×
IT

Ask Slashdot: How Do You Deal With Priorities Inflation In IT Projects? 304

NetDanzr writes "I work for an IT company that has a steady stream of projects, new features to our existing products and technical support issues. As it is customary, though, our development resources are not sufficient to cover the amount of projects. As a result, our delivery dates are slipping, and as a result the average priority of projects is rising. Where the goal was to have only 10% of projects rated high, within a year nearly 50% of projects are rated as such. Our solution is to completely wipe out the project list once per year and start a new, properly prioritized list. How does your company deal with this inflation of priorities?"
This discussion has been archived. No new comments can be posted.

Ask Slashdot: How Do You Deal With Priorities Inflation In IT Projects?

Comments Filter:
  • Staff (Score:4, Informative)

    by MBGMorden ( 803437 ) on Monday February 20, 2012 @12:20PM (#39100047)

    Sounds like you're honestly understaffed. If you guys are honestly working as hard as possible and things are still going unfinished then its not a problem of priorities - it's a manpower problem. Hire more people.

  • by blue_teeth ( 83171 ) on Monday February 20, 2012 @12:40PM (#39100315)
    Companies underbid projects with aggressive timelines and less resources.  Theme these days is, get projects at any cost, we will figure it out once the project starts moving.

    Who/what is responsible for this?

    1.  Sales teams who put pressure on project architects for low costing.
    2.  Solution Architects who think each of their project member is Linus Torvalds.
    3.  Existence of bench resources.  Idea is to underbid and deploy bench resources (unbilled) as anyway they are idle.
    4.  Unbilled bench resources suddenly getting deployed in new projects.

  • by v1 ( 525388 ) on Monday February 20, 2012 @01:01PM (#39100527) Homepage Journal

    This is somewhat appropriate here I think. Frequentlyt, Dilbert [dilbert.com] is on-target when management is not.

  • by unixisc ( 2429386 ) on Monday February 20, 2012 @01:20PM (#39100737)
    One suggestion - for any feature creep, make it clear that it will
    • Delay the project by time t
    • Lower the priority of the project to the 5th or 6th in priority

    One of the problems w/ project management when one is bombarded w/ projects is that one has to have a continuous line of communication to the boss, which obviously means less time actually working. Oh, that, and meetings regarding the project as well. One solution is an online status tracking system that gives anybody an instant status level as to where in the project it's there. That way, one can determine where the bottleneck is, and work towards addressing it there.

  • by maple_shaft ( 1046302 ) on Monday February 20, 2012 @01:22PM (#39100767)

    Some companies have a group that only handles system-down and user complaints and other people handle the longer-term projects. Some companies have babysitters for upper management.

    This.

    You will be amazed how much more can get done on projects when you have dedicated Firefighers and Babysitters. Another helpful suggestion is to make sure that the Babysitters have teeth. Upper management is not going to care what IT processes are in place to keep the whole infrastructure from devolving into anarchy. They want what they want and they want it fast.

    Make sure your babysitters are the best of the best, and make sure that they can affect immediate change in IT without having to go through the proper channels. If they need to open a port on the firewall then they should have the passwords and access to do so. If they need to have an account created make sure that they can log into the LDAP server and create one, etc...

    So many IT people get angry about this claiming that they shouldn't get special treatment. Bullshit. They should get special treatment because they are the Upper Management, they are pretty damn special. You don't want them waiting and you don't want their IT requests to slow down the project guys at all.

  • by GreyyGuy ( 91753 ) on Monday February 20, 2012 @04:49PM (#39103049)

    Ye flipping gods- another one.

    No. Just No.

    Sarbanes-Oxley did NOT make it illegal to change production software in public companies. What it DID do was make it a requirement that the management of a company was legally responsible for the financial reporting of the company. So even if the financial reporting software had a problem, they are still on the hook for it. All the IT auditing firms got together and agreed that meant the FINANCIAL software needed to have all the changes be approved by the proper applications owners and that there needed to be an approval process, documentation, and all the other stuff that makes auditors (and no one else) happy.

    Those same auditors have pushed that in order to avoid risk, EVERY software application should go through that same process even if it has nothing to do with finance. Risk-adverse management agreed. So now most public companies force Sarbanes-Oxley compliant processes on every bit of development, costing huge amounts of wasted time and money.

    Skipping it doesn't mean it is illegal. It means that if your company is audited and a set of software is found to be the cause then it is possible the management might get fined. To the best of my knowledge, this has NEVER happened. And I feel comfortable saying it is unlikely to ever happen.

Our business in life is not to succeed but to continue to fail in high spirits. -- Robert Louis Stevenson

Working...