This section contains the following topics:
Access the Detailed Management Views
Risks, Issues, and Change Requests
To access a management view, click a management view from the Management Views menu.
Use the views menu to view management and executive summary data of PMBOK Guide project documents. For example, you can view a detailed list of all the project reports to which you have access using the project reports page.
Some details include the project name to which the document is associated, the document name or title, and the statuses for review, quality, and scope. Some of the management views have tabs, which you can click to view document-specific data in portlets on the page.
The project charters page is a management summary view. The page includes data from all the project charter documents for the PMBOK Guide projects to which you have access. Each item in the list represents a project charter document. If a project charter document does not exist, the list is empty. You can click the document title to open the document.
By default, the documents submitted for review display in the list. You can use the Approval Status filter field to see documents that are still in draft.
To view this page, click Project Charters from the Management Views menu.
You can view details from the project charter documents using the following columns displayed on the page:
Defines the title for the document. Once you submit the document for review, this field becomes display only. In management views, you can click the document title to open the document.
Limit: 80 characters
Displays the name of the project to which this document is associated. Click the project name to open the project.
Displays the name of the resource managing the project associated with this document. Click the project manager name to open the resource properties page. The value for this field is based on the Manager field on the project properties page.
Displays the date the document was last updated and saved.
Displays the date this document was approved or rejected.
Displays the approval status for the document as a stoplight.
Values:
Stoplights:
Displays the number of days the document is undergoing review and a stoplight to represent the number of days. If you submit the document for review and it is being reviewed, the number and stoplight displays. If the document is not submitted for review, or is approved or rejected, the field is rendered empty.
Stoplights:
Displays the defined purpose or business need for this project. The data for the field is derived from the Purpose/Business Need field on the project charter properties page.
The project reports page is a management summary view that includes details on the project report documents to which you have access. Each item in the list represents a project report document. If no project report documents exist, the list is empty. You can click the report name to open the document.
To view this page, click Project Reports from the Management Views menu.
You can view details from the project report documents using the following columns that display on the page:
Displays the name of the project to which this document is associated. Click the project name to open the project.
Displays the name of the document. You can click the document name to open the document.
Displays the date the document was last updated and saved.
Displays the review status for the document at the time of creation. In management views and in list views, the field displays as a stoplight.
Values:
Stoplights:
Displays the number of days the document is undergoing review and a stoplight to represent the number of days. If you submit the document for review and it is being reviewed, the number and stoplight displays. If the document is not submitted for review, or is approved or rejected, the field is rendered empty.
Stoplights:
Displays the date that the project manager submitted the document for review.
The scope status for the project relative to the project objectives. The value for the field is derived from the project report properties page. When viewing the field in portlets, the status displays as a stoplight.
Values:
Stoplights:
Specifies the schedule status for the project. The value for the field is based on the following checks performed in the order listed:
Stoplights:
Specifies the status of the cost for the project plan based on the project planned cost amount. The cost amount is a field on the budget page of project properties. Once you submit the project report document for review, this field is display only. In management views, the status is display only.
Values:
Specifies the status of the quality for this project plan. Once you submit the document for review, this field displays as a stoplight to represent the project quality.
Values:
Stoplights:
Specifies the status of the project outlook. The field displays a check mark on the project report properties page. The status displays as a stoplight in portlets.
Values:
Stoplights:
Managers and executives can use the Risks, Issues and Change Requests view to view data across all PMBOK Guide projects in an organization. Project managers can also use this view to view metrics across all their assigned PMBOK Guide projects.
The risks page is the default page that opens when you click Risks, Issues and Change Requests from the Management Views menu. From this page you can access the following other pages from the dashboard:
You can view a detailed summary of all of the risks to which you have access using the project risks portlet. This portlet displays on the risks page.
This page includes the following columns:
Displays a yellow check mark to indicate that the risk score has exceeded the risk threshold. The risk threshold is the acceptable level of risk that can be tolerated without acting out the risk response strategy. The threshold is based on the impact and probability factors. This is a system-level value for all projects that the CA Clarity PPM administrator sets. The value for this field is based on the Impact and Probability fields on the risk properties page.
Displays the probability that the impact occurs in the form of a stoplight. The risk probability is used to calculate the risk exposure.
Stoplights:
Displays the effect of the particular risk on the project, determined by the risk effect on the project performance, supportability, cost, and schedule. This risk impact is used to calculate the risk exposure.
Stoplights:
Displays the unique identifier assigned to the risk for tracking.
Displays the short name for the risk.
Limit: 64 characters
Displays the name of the project to which this document is associated. Click the project name to open the project.
Displays the risk category assigned to this risk.
Values: Objectives, Sponsorship, Funding, Resource Availability, Interdependencies, Technical, Human Interface, Organizational Culture, Supportability, Implementation, and Flexibility.
Displays the resource who manages the risk. This resource is responsible for ensuring that the risk is managed and tracked appropriately through its lifecycle. If an issue or change request is created from this risk, the owner information is carried over to the issue or change request.
Opens an email from your default email client addressed to the resource who created the request.
Displays the target date of resolving the risk. This date is the same or earlier than the impact date.
You can view a detailed summary of all of the issues to which you have access using the project issues portlet. This portlet displays on the issues page.
This page includes the following columns:
Displays the schedule status for the project. If a project report document exists, the value for this field is based on the Schedule Status field on the Project Report Properties page. If a project report does not exist, then the value for this field is based on the Baseline Finish Date field on the Baseline Revision Properties page. This field displays as a stoplight to represent the project's schedule status.
Important! For the stoplight to display a color, you must first baseline the project.
Values:
Stoplights:
Displays the priority level of this issue.
Values: Low, Medium, and High
Displays the unique identifier assigned to the issue for tracking.
Defines the short name for the issue.
Limits: 64 characters
Displays the name of the project to which this document is associated. Click the project name to open the project.
Displays the category to which the issue is assigned.
Values: Flexibility, Funding, Human Interface, Implementation, Interdependencies, Objectives, Organizational Culture, Resource Availability, Sponsorship, Success Risk, Supportability, or Technical
Displays the name or the resource managing the issue. This resource is responsible for ensuring that the risk is managed and tracked appropriately through its lifecycle. If an issue or change request is created from this risk, for example, the owner information is carried over to the issue or change request.
Opens an email from your default email client addressed to the resource who created the request.
Displays the target date of resolving the issue. This date is earlier than the impact date.
You can view a detailed summary of all of the change requests to which you have access using the project change requests portlet. The portlet displays on the change requests page.
This page includes the following columns:
Displays the priority level of the change request.
Values: Low, Medium, and High
Displays the change request unique identifier.
Defines the short name for the change request. In portlets, this field is read only except when it displays in a portlet to edit. If this field is displayed as a link in a portlet, click the name to open the change request properties page.
Limit: 64 characters
For more information, see the Basics User Guide.
Displays the status for the change request.
Values: Open, Work in Progress, Closed, and Resolved
Displays the project name. You can click the name to open the project properties page.
Displays the name of the resource who created the request.
Displays the name of the resource managing the request. This resource is responsible for ensuring that the request is managed and tracked appropriately through its lifecycle. If an issue or change request is created from this risk, for example, the owner information is carried over to the issue or change request.
Opens an email from your default email client addressed to the resource who created the request.
Specifies the expected date of closing the request.
Managers and executives can use the Lessons Learned view to view data for lessons learned documents that have been submitted across all PMBOK Guide projects in their organization. Project managers can also use this view to view metrics across all their assigned PMBOK Guide projects. The projects that display in the list are those to which you have access rights. The list does not include project templates.
To view this detail view, click Lessons Learned from the Management Views menu.
You can view details for submitted documents using the following columns:
Displays the category for this lessons learned document.
Values: Process Change, Framework/Methodology, Technology Change, Organizational Change, Other, and TBD.
Defines the title for the document. Once you submit the document for review, this field becomes display only. In management views, you can click the document title to open the document.
Limit: 80 characters
Displays the name of the project to which this document is associated. Click the project name to open the project.
Displays the name of the resource managing the project associated with this document. Click the project manager name to open the resource properties page. The value for this field is based on the Manager field on the project properties page.
Displays the date the document was last updated and saved.
Displays the date that the project manager submitted the document for review.
Displays the review status for the document at the time of creation. In management views and in list views, the field displays as a stoplight.
Values:
Stoplights:
Managers and executives can use the Executive Dashboard to view data across all PMBOK Guide projects in an organization. Project managers can also use this dashboard to view metrics across all their assigned PMBOK Guide projects. The list displays the projects you have access to.
By default, the data displayed in the portlets on this page is derived from active projects only. You can view the project data, including inactive project data, by using the filter fields.
The projects status page is the default page that opens when you click Executive Dashboard from the Management Views menu. From this page, you can access the following other pages from the dashboard:
Use the Project Status portlet that displays on the projects status page to view PMBOK Guide metrics and status information across all your assigned PMBOK Guide projects. The list displays the projects you have access to.
For more information, see the Project Management User Guide.
The following fields are displayed on the portlet:
Displays the name of the project to which this document is associated. Click the project name to open the project.
Displays the project phase for this project. In management views, the phase displays in a bar graph. The shaded area indicates the phase for the project. You can roll your cursor over the bar to view the phase status, the progress, and the total number of phases for that project. The value for this field is based on the Phase field on the project properties page.
Displays the name of the resource managing the project associated with this document. Click the project manager name to open the resource properties page. The value for this field is based on the Manager field on the project properties page.
Displays the date of starting the project. The value for this field is based on the Start Date field on the schedule page of project properties.
Displays the date of completing the project. The value for this field is based on the Finish Date field on the schedule page of project properties.
Displays the date of starting the project baseline revision, if a baseline on the project exists. The value for this field is based on the Baseline Start field on the baseline revision properties page.
Displays the date of completing the project baseline revision, if a baseline on the project exists. The value for the field is based on the Baseline Finish field on the baseline revision properties page.
Displays a stoplight to represent the project status level with risks. The value for the field is based on the highest probability of open risks entered on the risks page.
Stoplights:
Displays the project status level with issues in the form of a stoplight to represent the status. The value for this field is based on the Status field on the issue properties page.
Default: Open
Stoplights:
Displays a check mark if at least one change request is logged for the project. You can mouse over the check mark to display the number of change requests created in the rollover text.
The scope status for the project relative to the project objectives. The value for the field is derived from the project report properties page. When viewing the field in portlets, the status displays as a stoplight.
Values:
Stoplights:
Specifies the schedule status for the project. The value for the field is based on the following checks performed in the order listed:
Stoplights:
Specifies the status of the cost for the project plan based on the project planned cost amount. The cost amount is a field on the budget page of project properties. Once you submit the project report document for review, this field is display only. In management views, the status is display only.
Values:
Specifies the status of the project outlook. The field displays a check mark on the project report properties page. The status displays as a stoplight in portlets.
Values:
Stoplights:
You can view the project variance and performance data of all active PMBOK Guide projects within your organization using the project variance and performance portlet. The list displays the projects you have access to. The portlet displays on the project variance and performance page.
The following fields are displayed on this portlet:
Displays the name of the project to which this document is associated. Click the project name to open the project.
Displays the name of the resource managing the project associated with this document. Click the project manager name to open the resource properties page. The value for this field is based on the Manager field on the project properties page.
Displays the planned date of starting that the project based on the current baseline. The value for this field is derived from the baseline revision properties page.
Displays the planned date of completing the project based on the current baseline. The value for the field is derived from the Baseline Finish field on the baseline revision properties page.
Displays the system-calculated value of estimate at completion (EAC), which is the total cost of all actual work completed to date plus the predicted cost finishing the remaining work, based on the following formula:
EAC = AC + ETC
Displays the total planned value for the project, which is also known as the Planned Value (PV). The Budget at Completion (BAC) is the authorized budget assigned to the work yet to start for a project or work breakdown structure component. This value is system-calculated.
Displays the actual cost (AC) at the task level, which is the total cost incurred and recorded in performing the project work, or work breakdown structure component. The actual cost is the total cost incurred in performing the work that the EV measured.
Displays the planned value (PV) is a system-calculated value representing the Budgeted Cost of Scheduled Work (BCWS). PV is the authorized budget assigned to the project work not started, or a work breakdown structure component. The total planned value for the project is also known as Budget At Completion (BAC).
PV is calculated based on the following formula:
Planned Value (PV) = Sum of BAC through a point in time
Displays the earned value (EV) is system-calculated and represents the Budgeted Cost of Work Performed (BCWP). EV is the value indicated in the the approved budget for project work performed, or work breakdown structure component.
EV is calculated using the following formula:
Earned Value (EV) = Budget At Completion (BAC) for a task x % Complete
Displays the cost variance (CV), which is the value of work accomplished as against the amount spent to date.
CV is calculated using the following formula:
Cost Variance (CV) = Earned Value (EV) - Actual Cost (AC)
Displays the system-calculated value of the schedule performance index (SPI). The value represents the ratio of work performed to work scheduled.
SPI is based on the following formula:
Schedule Performance Index (SPI) = Earned Value / Planned Value
Note: A value less than one indicates the work is behind schedule.
Displays the system-calculated value of Cost Performance Index (CPI), which is an efficiency rating for work accomplished.
CPI is based on the following formula:
Cost Performance Index (CPI) = Earned Value / Actual Costs
Note: A value greater than one indicates the costs are running over budget.
The project by phases portlet displays a bar chart of those projects to which you have access. The portlet displays on the project by phases page of executive dashboard. The portlet is designed for senior executives or senior users to view phase data across all PMBOK Guide projects in their organization and to which they have access. The list only includes projects and not project templates.
The bar displays the project count in each phase. You can roll your cursor over a bar to display the percentage of PMBOK Guide projects that are at a particular phase. The percentage is based on the following calculation:
The number of PMBOK Guide projects per phase / the number of PMBOK Guide projects
The default phase type displayed in Standard. You can use the filter to view projects in phases for different phase types.
The following field is displayed on this portlet:
The phase for this project. This metric is used in portfolio management analysis.
Values for Standard Phase Type: Requirements, Design, Build, Test, and Launch
|
Copyright © 2013 CA.
All rights reserved.
|
|