CIO has just come up with their list of the 14 most common mistakes IT departments make. It really is a good read and with IT becoming more and more a critical part of a business if not the core business itself, it would do project managers some good to check out the list and see how to avoid these mistakes. A successful IT dept needs to be like a US Olympic basketball team with improved teamplay if they plan to successfully complete a toughest of projects.
- Projects lack the right resources with the right skills.
- Projects lack experienced project manager. – I like this one because usually what happens is a project manager may have a ton of experience or a lot of technical knowledge when what he should have is a fair amount of both. I used to know this guy who was a marketing manager for like 14 years and when they transferred him to spearhead a tech support endeavor he was just horrible at it.
- IT doesn’t follow a standard, repeatable project management process. – This was actually a case that I made with my college thesis because the company that we were studying had decided to outsource their SCM system and then the company ended up using pretty much the same system that they had developed for a different company that wasn’t even the same industry as our subject company. So they ended up not using the system at all etc etc.
- IT gets hamstrung by too much process.
- They don’t track changes to the scope of the project.
- They lack up-to-date data about the status of the projects.
- They ignore problems. – hey kinda like what Microsoft did when they pushed xbox 360 with major defects just so they can release it earlier than the PS3
- They don’t take the time to define the scope of a project.
- They fail to see the dependencies between projects.
- They don’t consider Murphy’s Law. “If anything can go wrong, it will.” Longer versions “If there’s more than one possible outcome of a job or task, and one of those outcomes will result in disaster or an undesirable consequence, then somebody will do it that way””Whatever can go wrong will go wrong, and at the worst possible time, in the worst possible way”
- They give short shrift to change management.
- Project schedules are incomplete.
- IT doesnt push back on unreasonable deadlines.
- They dont communicate well with project sponsors and stakeholders.
check out the full article here.