Introduction
I’m tough on project managers. In my career, I been privileged to work with some of the very best project managers and cursed to work some of the very worst. In this series of articles, I hope to open a dialogue about things that worked very well and things that didn’t work so well. More important, I hope to discuss why these things worked well or didn’t.
Project Management is a Hard Job
Project management is a lot of work. If you don’t believe me, try it sometime. Better yet, try it when the next mortgage depends on how well you do.
For the DBA; almost anyone can look like a rock star DBA as long as the jobs and backups are all completing successfully, queries return data quickly, and there’s no contention on the server. Comparing the PM job to that of DBA; almost anyone can look like a rock star PM as long as the customer is happy, work is rolling in on time, tests are succeeding, and scope and customer expectations are being managed.
Some of it is the DBA or PM. Some of it is the project / job.
The Project Manager is in a Position of Trust and Responsibility
Like the DBA, the PM is in a position of trust with the customer or management. PMs are entrusted with more than simply interpreting the customer’s desires, goals, and needs; they’re entrusted with making sure developers and DBAs (you and I) understand them. I don’t know if you’ve tried that lately, but that’s a tall order.
First, the PM has to understand the customer’s requirements. Think about that for a minute. Communication is never 100%. Something is always left out, or forgotten, or misunderstood. Right out of the chute, error is introduced. And then the project manager communicates their understanding of the issues to the development team. The opportunities for miscommunication are manifold:
- The customer / stakeholder may leave information out.
- The PM may misunderstand.
- In communicating to the team, the PM may leave information out.
- Development team members may misunderstand.
Minimizing communication errors is crucial.
Applied Communications
The developer or DBA is at the end of the chain of communication. By the time the information is communicated to the developer / DBA, it’s been filtered at least twice.
What I Wish Project Managers Knew…
… about communications: Communications errors are endemic in projects. Anticipate them, manage them, don’t be surprised when they occur. Have a plan – and time built into the plan – for managing miscommunications and cleaning up the ensuing mess.
Your choices are: Perfect communication, or be prepared to manage and mitigate miscommunications. I vote for the latter.
:{> Andy

Comments