Dr. Project: Ailing IT Project

 

I inherited an internal software application development project that has been languishing for more than a year and is still in the analysis stage. It has come to my attention that the original team only evaluated two commercially available packages before deciding to bring the project in-house. I have since discovered 4-5 additional packages that look as if they could provide the necessary functionality. The Executive Sponsor is anxious for a solution. Same project, different problem. I have been assigned to this project as the business unit project manager for two months now and a reorganization of our information systems department will bring about an assignment of a project manager from that department as well. How do we divide responsibilities, etc.? Any advice? Thanks!

Tommie

Dear Tommie,

Have you recently reviewed your family genealogy? I am wondering how you inherited this poorly researched software application development project from a distant uncle twice removed that you met at a family reunion 10 years ago. Fortunately for you, the 13th Law of Project Management applies to your situation: It's the last project manager's fault!

Seriously though, as a professional project manager you have one choice and that is to ask the anxious Executive Sponsor this: Would he or she rather move ahead with a poorly researched solution that will …

Please log in or sign up below to read the rest of the article.