Tip make sure that you break the work down so that

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: hat you break the work down so that tasks performed by individual groups or departments are identifiable. This will enable you to report performance group by group or department by department and still roll totals up to report for the entire project. The information you plan to communicate will drive your activities throughout the project. Your plans should include the metrics that must be gathered in order to support the information you plan to communicate. You will need to identify who is responsible for providing the information and where the information is to be stored and reported from. There are two questions you need to ask yourself before you commit to providing a report: 1. How do I get this information? (i.e. what metrics do I need to capture and where will they come from) 2. Where will I store the metrics? A failure to answer both questions will mean that either you have to alter your plan to task someone to gather the metrics, identify a tool to capture and retrieve the metrics, or drop the requirement. Finally, don't forget individual accomplishments and rewards when reporting project progress. There's nothing like a good news story to keep team morale high and the celebration of a team member's accomplishment is something most sponsors enjoy hearing about. How to Communicate There are many different means of communication available to you - face to face, e-mail, Intranet, Internet, regular mail, phone, video conferences, etc., etc. These can be grouped into 2 groups: "push" communications and "pull" communications. Push communications requires you to push the information onto the recipient as the name would suggest, while pull communications requires the recipient to actively retrieve the information from a central source. Websites and centralised repositories are examples of pull communications, while e-mail and meetings are examples of push communications. Preference for either push or pull communications is typically a personal preferenc...
View Full Document

This document was uploaded on 12/31/2013.

Ask a homework question - tutors are online