 |
Typical Key Features for the Report Status Service
03 July 2009
Typical Key Features for the Report Status ServiceHere is an example of a typical online project management key features table for the Report Status Service. Key Service Features and Benefits For the Report Status Service As of 3/1/2007 | Feature | Information | Service Name: | Report Status Service | Launch Date: | 3/1/2007 | PMO Contact Name: | Ariel Johnson, PMO Communications Manager | Contact Information for PMO Contact | CommunicationsManager@pmo.oucompany.com | Benefits | Benefit Name | Beneficiary | Notes | Greater chance of on-time, on budget delivery of acceptable results | Whole company Each project | Providing executives with up-to-date status information allows prompt identification and resolution of issues, helping ensure project success. | Reduced organizational risk | Whole company Senior executives | Serious problems with projects identified earlier, allowing executive intervention to fix or cancel project. | Better strategic planning | <!--[if !supportLists]-->§ <!--[endif]-->Whole company <!--[if !supportLists]-->§ <!--[endif]-->Senior executives | Summarized portfolio status from all projects allows better projections for planning future projects. | Greater customer satisfaction | <!--[if !supportLists]-->§ <!--[endif]-->External customers of projects <!--[if !supportLists]-->§ <!--[endif]-->Whole company <!--[if !supportLists]-->§ <!--[endif]-->Projects with external customers | For those projects with external customers, a weekly summary will be delivered to the customer. This will help keep the customer on board and involved, and identify any miscommunications or issues early, so that they can be resolved. |
|
|
|
|
|
| | | | | |
These notes explain common exceptions or differences that may be appropriate to some PMOs. <!--[if !supportLists]-->§ <!--[endif]-->Depending on the needs of the organization, status reporting may focus on the entire portfolio, programs of projects grouped together, or individual projects <!--[if !supportLists]-->§ <!--[endif]-->Companies that perform projects for external customers are likely to want to prepare two different status summaries: one for internal use only, and another for external customers. <!--[if !supportLists]-->§ <!--[endif]-->Companies that rely on ongoing services from vendors throughout project development are likely to want to send an external summary of project status report to vendors, or maybe an excerpt reporting only the performance of that vendor.
Copyright © Method123 Ltd 2000-2010
|
|
|
|
