The July 2008 issue of PMWorldToday (an informative global project management e-zine, by the way) has an interesting article for tech PMs and others working on technology projects: Avoiding the Top Five Traps of Technical Project Management (PDF). It's written by Bob McGannon, PMP, who has a long history of providing solid project management training, consulting, & coaching services. He shares his experience in working on technology projects and provides tips for avoiding some common "traps" when managing them. Here's an excerpt:

Managing technology projects can be one of the most challenging arenas of project management. Ironically, it is rarely the technology itself that presents obstacles for the technical project manager. Being mindful of the most common traps that await the unsuspecting project manager can help ensure your technical projects don’t end up as financial disasters that don’t deliver expected function, and diminish the reputation of yourself and your technical organization.

1. It is about business process, not the technical tool

The intent of a project is to move the business to a better place. That better place can mean increased efficiency, additional capabilities or an improvement in the accuracy of the business’ output. Regardless of the nature of the business improvement, it is enhanced process that will drive the superior results. It is not necessarily as a result of a tool, a new IT system or improved technology – these are only the catalyst for the improved process which drives business results. Many project managers and their teams mistake the new technology as being the output of the project, rather than the enhanced process that results in conjunction with implementing new technology.

Read the rest here (PDF): http://www.pmforum.org/library/tips/2008/PDFs/McGannon-7-08.pdf

The other four "traps" discussed include:

• 2. Moderate the amount of change your technology users must absorb
• 3. We understand the business better than our customer does!
• 4. There are no "small" changes
• 5. New function isn't necessarily new value

My thoughs - a decent list. #3 is very common - and not just to technology projects, and #4 "there are no small changes" would make a great tattoo for ANY project manager's forehead - or, at a minimum, burned into their memory for life!

Posted by Raven Young at Raven's Brain under Project Management
Technorati tags: Project Management, IT Project Management, Technology Projects, Project Management Blog, Project Management Posts