A sad tale of a how a sponsor/PM relationship killed a project...
Exec identifies a need for a project and nominates self as sponsor. PM gets assigned to project and assembles project team. Sponsor is vague about problem to be solved other than "we need a new system". PM can't communicate problem to be solved to the team because he doesn't understand what the problem is. Sponsor continues to ask for more and more things to be included in project, PM doesn't have courage to say no. PM treats sponsor as "that person in the corner office" and doesn't know how to ask for help, so he escalates everything. Sponsor has to make some tough decisions but is unwilling to do so because of the political fallout. PM provides bad information about decision alternatives so sponsor ignores him. Due to changing priorities project no longer makes sense to do, but PM lobbies to keep the project going. Sponsor loses interest because there are bigger fish to fry. PM and team are disillusioned because sponsor doesn't care. Project dies a slow death. R.I.P.
While this is a fictional story, you can undoubtedly relate to most of these things happening on one project or another in your career. The sponsor/PM partnership on a project is one of those "soft skill" factors that gets frequently overlooked when assessing a PM's skills but is a key determinant in the success or failure of a project. Under a healthy partnership, the sponsor and PM work as a singular unit to ensure the project gets what it needs to be as successful as possible using only as many resources as absolutely necessary to secure success. Under a less than healthy relationship the project will undoubtedly cost more in time and money assuming it even gets completed at all.
Throughout my career I've been both a sponsor and a PM and have first-hand experience in how this relationship needs to work from both sides of the desk. Through my experience, I've locked down on ten truths which I feel are crucial to securing a healthy sponsor/PM partnership. See if these resonate with you:
Recently I was asked by a journalist how I practiced public speaking. At this point in my life, getting up in front of an audience is pretty much second nature. However, it wasn't always so. I had to work hard at the skill and had to fail A LOT before I found my schtick and was able to get pretty OK at it.
Here are the highlights from the interview along with six take-aways to help you be a better public speaker.
So okay, Microsoft Project is a super flexible tool in helping you as a project manager define your project tasks, dependencies, and resources. Quite frankly, though, the workplan you define in MS Project is only as good as the thought that goes into it. Too often I've seen savvy MS Project users completely bungle a project because, while the tool was being used appropriately, the workplan didn't make sense to the project team and didn't reflect what really needed to be done. The team consistently expressed confusion about what needed to be done by when because the project workplan wasn't reflective of the actual work which needed to be done. Great exercise in using MS Project, but poor execution of the project. Blech.
Contact Lonnie about article reprints. Please specify article you wish to reprint.
See Lonnie's Amazon Author Page