Discussion on:

Project communications: A plan for getting your message across

Project success is about being on time, to cost and quality. However you can meet all of these and still have your project deemed a failure. The reason for this is poor stakeholder management. The only way to managestakeholders is by talking. Reports are good, but face to face (or at least voice to voice is essential). I always ensure that I have regular catch ups with senior stakeholders and team members. No issues came as a suprise to them at the Project Board meetings, and they were always aware of what they needed to do to resolve issues. On one project I delivered we were 6 months late (due to external dependencies) but the key customer was still extatic with the delivery, and saw it as the best project they had had delivered from the IT function. And the reason was because all along they new what was happening.

When there are 4 people attending a meeting, how many channels of
communication are possible?

Thanks for the great article! I agree that communication with your team is your everything. To monitor progress, to receive early warning of danger, to promote cooperation, to motivate through team involvement, all of these rely upon communication. In Wrike we also believe that your project communications should be integrated into your planning process to make keeping schedules up-to-date easier. Do you agree?

Thanks for the detailed information on this subject. I found it very helpful in writting my paper. I was very pleased to see that my ideas on effective communication are within the above average percentage of others.

How about the significance of employing softwares like primaver/ms project in revealing the exact position of the project state as and when required? let us discuss this ,