IT departments are either the darlings or the despised of corporate America, and some practitioners would debate which extreme causes the most pain. Let's face it, nowa-days the reward for doing a great job is more work. Once an IT group earns the trust of business units, it must then survive the onslaught of new projects.
Good organizations, like good bosses, don't want you to suck in more than you can handle and implode in the process—our research shows high-performing businesses want IT to stem the tide. And make no mistake: The tide needs to be stemmed. In our recent survey of 986 IT and business managers, 75% said the IT workload was either heavy or crushing.
In its simplest and most useful form, PPM involves setting parameters around, classi-fying, and prioritizing all projects. When you get right down to it, apart from geeky certifications and expensive software, PPM is something we do every day when we decide to go to work rather than fishing or pick up our children from daycare rather than heading to the gym first. Sure, doing IT PPM right isn't as automatic, but it's not rocket science, either.
Failure By Any Other Name
The highest performers in the IT world, as defined in a recent study by the IT Process Institute, are those most likely to cancel projects—at a rate double that of their lower-performing counterparts, in fact.