Previous Topic: ProjectsNext Topic: Management Views


Documents

This section contains the following topics:

How to Work with PMBOK Guide Documents

Product Description Documents

Project Charter Documents

Project Scope Statement Documents

Scope Management Plan Documents

Quality Management Plan Documents

Risk Identification - SWOT Analysis Documents

Project Report Documents

Lessons Learned Documents

Project Closure Documents

How to Work with PMBOK Guide Documents

The following process details how to work with PMBOK guide documents:

  1. The project manager creates one of the following documents:
  2. The project manager edits access to the documents.
  3. If necessary, the project manager edits the document:
  4. Depending on the type of document, the project manager submits the document for review or approval. An action item is sent to the reviewer.
  5. Depending on the type of document, the reviewer does one of the following:

Manage Access to PMBOK Guide Documents

You can manage access to the PMBOK Guide documents using the links in the Access to this Object displayed when the document is open. Use the links to view, grant, and edit access rights to your document.

Contact your CA Clarity PPM administrator or see the Administration Guide for more information.

Submit Documents for Review

Not all documents require approval, but they all require review. When you submit a document for review, the document approval or document review process starts. The reviewer is sent an action item to review and/or approve the document. The process that is triggered to start is dependent on the type of document you are submitting for review.

Note: The scope management plan, quality management plan, and risk identification - SWOT analysis documents cannot be submitted for review.

The project manager can change the resources identified as reviewers by editing the names listed in the Reviewers field on the project properties page.

Once you submit your document for review, all the document fields become display-only.

Follow these steps:

  1. Open the project.

    The properties page appears.

  2. Open the document to submit for review.

    The properties page for that document appears.

  3. Select the check box for the Submit for Review field that displays in the General section of the page, and submit.

    The document is submitted for review.

More information:

How to Work with the Document Approval Process

How to Work with the Document Review Process

Document Review and Approval Processes

Review Documents from Action Items

Project managers are responsible for creating PMBOK Guide documents and for submitting them for review. PMBOK reviewers receive action items to review the submitted documents in their Organizer. The reviewer reviews the document and marks completion with the "Reviewed" status.

For more information, see the Basics User Guide.

Follow these steps:

  1. Open the Personal menu and click Organizer.

    The organizer action items page appears by default.

  2. Locate the action item, choose a status from the Status field for the action item, and save.

    Values: Reviewed, Not Reviewed

    Default: Not Reviewed

More information:

How to Work with PMBOK Guide Documents

Manage Access to PMBOK Guide Documents

Submit Documents for Review

Review and Approve Documents from Action Items

Document Review and Approval Processes

Review and Approve Documents from Action Items

Project managers are responsible for creating PMBOK documents, providing product descriptions and project charters, and submitting for approval. The resource, assigned as the reviewer of product description documents, receive an action item in their Organizer when the project manager submits the document for approval. The reviewer reviews the document and completes the action item marking the status as "Approved" or "Rejected".

Follow these steps:

  1. Open the Personal menu and click Organizer.

    The organizer action items page appears by default.

  2. Locate the action item, review the document, select a status from the Status field for the action item, and save.

    Values: Approved, Rejected, Open

    Default: Open

    The status of the action item is saved.

More information:

How to Work with PMBOK Guide Documents

Manage Access to PMBOK Guide Documents

Submit Documents for Review

Review Documents from Action Items

Document Review and Approval Processes

Product Description Documents

The product description document records the description of the product or service related to the project.

See A Guide to the Project Management Body of Knowledge (PMBOK Guide) for more information.

See the PMI® Compendium of Project Management Practices for more information.

Create Product Description Documents

Once you save the document, many of the fields in the General section of the properties page become visible, some of which are display only.

Follow these steps:

  1. Open the PMBOK Guide project.

    The properties page appears.

  2. Open the Properties menu, and click Product Description.

    The product description page appears.

  3. Click New.

    The create page appears.

  4. Complete the following fields in the General section:
    Title

    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

    ID

    Displays the unique identifier for the document.

    Limit: 80 characters

  5. Complete the following fields in the Report Information section:
    Product or Service

    Defines the name of the product or service.

    Purpose

    Defines the purpose for the product or service.

    Full Explanation

    Defines the full explanation of the product or service.

  6. Complete the following fields in the Draft of Full Product or Service Description section:

    See A Guide to the Project Management Body of Knowledge (PMBOK Guide) for more information.

  7. Define the following remaining fields in the Draft of Full Product or Service Description section, and save:
    Attachment(s)

    Specifies the attachments associated with the document.

    Description of Attachment(s)

    Defines the description of the attachments associated with the document.

    Limits: 2000 characters

    The product description document is created.

More information:

Product Description Documents

View List of Product Description Documents

Edit Product Description Documents

View List of Product Description Documents

Use the product description page of project properties to view a list of product description documents. The details include the document title, approval status, the date the document was last updated, the date the product description was submitted, the date the product description was approved, and the number of days the document is in review.

To view the page, open the project, and from the Properties menu, click Product Description.

The following details display on the page:

Title

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

Approval Status

Displays the approval status for the document as a stoplight.

Values:

Stoplights:

Last Updated Date

Displays the date the document was last updated and saved.

Submitted Date

Displays the date that the project manager submitted the document for review.

Approved Date

Displays the date the document was approved or rejected.

Days in Review

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:

Edit Product Description Documents

The properties page is the default page that displays when you open this document. The fields on the page are defined in the General section when you first created the document. Additional fields are also displayed that you require completing before you submit the document for approval.

The fields for the other sections of the document are displayed on separate pages, which you can access from the properties menu. You can edit many of the fields displayed on the pages. Some, though, are display only.

Follow these steps:

  1. Open the project.

    The properties page appears.

  2. Open the product description document.

    The product properties page appears.

  3. Edit the following fields in the General section, and save:
    Title

    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

    ID

    Displays the unique identifier for the document.

    Limit: 80 characters

    Prepared By

    Displays the name of the resource who created the document.

    Limit: 80 characters

    Last Updated Date

    Displays the date the document was last updated and saved.

    Approval Status

    Displays the approval status for the document as a stoplight.

    Values:

    • New. The document is in draft mode and not submitted for approval.
    • Submitted for Review. The document is submitted for approval but not approved.
    • Approved. The document is submitted for approval and approved.
    • Rejected. The document is submitted for approval and rejected.

    Stoplights:

    • Grey. The approval status is "New" and not submitted for approval.
    • Yellow. The approval status is "Submitted for Review" but not approved.
    • Green. The approval status is "Approved". The document is submitted for approval and approved.
    • Red. The approval status is "Rejected". The document is submitted for approval and rejected.
    Submit for Review

    Specifies to submit this PMBOK Guide project document for review. Select the check box to submit the document for review.

    Default: Cleared

Project Charter Documents

The project charter document records the existing project.

See A Guide to the Project Management Body of Knowledge (PMBOK Guide) for more information.

See the PMI® Compendium of Project Management Practices for more information.

Create Project Charter Documents

Follow these steps:

  1. Open the PMBOK Guide project.

    The properties page appears.

  2. Open the Properties menu, and click Product Charter.

    The project charter page appears.

  3. Click New.

    The create page appears.

  4. Complete the following fields in the General section:
    Name

    Defines the name of this project charter. Once you submit the document for review, this field is display only. In management views, the title is the name of the project charter and is the project link. On the project dashboard page, the document name represents the project charter and is a link to the project charter.

    Limit: 80 characters

    ID

    Displays the unique identifier for the document.

    Limit: 80 characters

  5. Complete the following fields in the Overview section:

    See A Guide to the Project Management Body of Knowledge (PMBOK Guide) for more information.

  6. Complete the following fields in the Assumptions, Constraints and Issues section:

    See A Guide to the Project Management Body of Knowledge (PMBOK Guide) for more information.

  7. Complete the following fields in the Resources section:
    Personnel Resources

    Defines the resources that perform the tasks on this project. The resources who are not already on the project as team members are added to the project as team members when this document is approved.

    Financial Resources

    Defines the financial resources for this project charter.

    Important! If you define financial resources but not a detailed budget for the project, then when the reviewer approves this project charter, the project planned cost is populated with the value. If you have not defined the project planned cost start date and planned cost finish dates, the date fields are populated with the project Start Date and Finish Date field values. The Planned Cost, Planned Cost Start, and Planned Cost Finish fields appear on the budget properties page. The Start Date and Finish Date fields appear on the schedule page of properties page.

    Other Resources

    Defines the other resources for the project charter.

    Approach

    Defines the approach planned for this project.

  8. Complete the following fields in the Communication Plan section:

    See A Guide to the Project Management Body of Knowledge (PMBOK Guide) for more information.

  9. Define the following remaining fields in the Communication Plan section, and save:
    Attachment(s)

    Specifies the attachments associated with the document.

    Description of Attachment(s)

    Defines the description of the attachments associated with the document.

    Limits: 2000 characters

    The project charter document is created.

View List of Project Charter Documents

Use the project charter page to view a list of project charter documents, including details such as the document title, approval status, the date the document was last updated, the date the charter was submitted, the date the charter was approved, the number of days the document is in review, and the charter's business reason.

To view this page, open the project, and from the Properties menu, click Project Charter.

You can view the following details on the page:

Title

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

Approval Status

Displays the approval status for the document as a stoplight.

Values:

Stoplights:

Last Updated Date

Displays the date the document was last updated and saved.

Submitted Date

Displays the date that the project manager submitted the document for review.

Approved Date

Displays the date the document was approved or rejected.

Days in Review

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:

Purpose

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.

Edit Project Charter Documents

The properties page is the default page that displays when you open this document. The fields on the page are defined in the General section when you first created the document. Additional fields are also displayed that you require completing before you submit the document for approval.

The fields for the other sections of the document are displayed on separate pages, which you can access from the properties menu. You can edit many of the fields displayed on the pages. Some, though, are display only.

Follow these steps:

  1. Open the project.

    The properties page appears.

  2. Open the project charter document.

    The project charter properties page appears.

  3. Edit the following fields in the General section, and save:
    Name

    Defines the name of this project charter. Once you submit the document for review, this field is display only. In management views, the title is the name of the project charter and is the project link. On the project dashboard page, the document name represents the project charter and is a link to the project charter.

    Limit: 80 characters

    Designated Project Manager

    Defines the name of the resource designated as the manager for this project. Click the Browse icon to select a project manager.

    Default: The name of the project manager

    Submit for Review

    Specifies to submit this PMBOK Guide project document for review. Select the check box to submit the document for review.

    Default: Cleared

Project Scope Statement Documents

The project scope statement records the expectations for the project deliverables and objectives among the stakeholders.

See A Guide to the Project Management Body of Knowledge (PMBOK Guide) for more information.

See the PMI® Compendium of Project Management Practices for more information.

Create Project Scope Statement Documents

Follow these steps:

  1. Open the PMBOK Guide project.

    The properties page appears.

  2. Open the Properties menu, and click Project Scope Statement.

    The project scope statement page appears.

  3. Click New.

    The create page appears.

  4. Complete the following fields in the General section:
    Scope Statement Name

    Defines the name for this project scope statement document. Once you submit the scope statement for review, this field is display only.

    ID

    Displays the unique identifier for the document.

    Limit: 80 characters

  5. Complete the following fields in the Scope Statement Information and Project Objectives sections, and save:
    Attachment(s)

    Specifies the attachments associated with the document.

    Description of Attachment(s)

    Defines the description of the attachments associated with the document.

    Limits: 2000 characters

    See A Guide to the Project Management Body of Knowledge (PMBOK Guide) for more information.

    The project scope statement document is saved.

View List of Project Scope Statement Documents

Use the project scope statement page to view a list of project scope statement documents. Details include the document name, review status, the date the document was last updated, the date the document was submitted, the date the review was completed, and the number of days the document is being reviewed.

To view the page, open the project, and from the Properties menu, click Project Scope Statement.

You can view the following details on the page:

Scope Statement Name

Defines the name for this project scope statement document. Once you submit the scope statement for review, this field is display only.

Review Status

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:

Last Updated Date

Displays the date the document was last updated and saved.

Submitted Date

Displays the date that the project manager submitted the document for review.

Review Completed Date

Displays the date the review for this document was completed.

Days in Review

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:

Edit Project Scope Statement Documents

The properties page displays, by default, when you open a document. You can view and edit the fields defined when you first created the document.

Follow these steps:

  1. Open the project.

    The project properties appears.

  2. Open the project scope statement document.

    The project scope statement properties page appears.

  3. View the following fields in the General section:
    Prepared By

    Displays the name of the resource who created the document.

    Limit: 80 characters

    Last Updated Date

    Displays the date the document was last updated and saved.

    Review Status

    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:

    • New. The document is in draft mode and not submitted for review.
    • Submitted for Review. The document is submitted for review but not reviewed by all reviewers.
    • Review Completed. The document is submitted for review and is reviewed.

    Stoplights:

    • Grey. The document not submitted for review.
    • Green. The document is submitted for review and the review is complete.
    • Yellow. The document is submitted for review but not reviewed.
  4. Edit the following field in the General section, and save:
    Scope Statement Name

    Defines the name for this project scope statement document. Once you submit the scope statement for review, this field is display only.

Scope Management Plan Documents

The scope management plan document records how the project management team plans to manage the project scope and handle changes to project scope.

See A Guide to the Project Management Body of Knowledge (PMBOK Guide) for more information.

See the PMI® Compendium of Project Management Practices for more information.

Create Scope Management Plan Documents

Follow these steps:

  1. Open the PMBOK Guide project.

    The properties page appears.

  2. Open the Properties menu, and click Scope Management Plan.

    The scope management plan page appears.

  3. Click New.

    The create page appears.

  4. Complete the following fields in the General section:
    Scope Management Plan Name

    Defines the name of this scope management plan document.

    Limit: 80 characters

    ID

    Displays the unique identifier for the document.

    Limit: 80 characters

  5. Complete the following fields in the Plan Information section:

    See A Guide to the Project Management Body of Knowledge (PMBOK Guide) for more information.

  6. Define the following remaining fields in the Plan Information section, and click Submit:
    Attachment(s)

    Specifies the attachments associated with the document.

    Description of Attachment(s)

    Defines the description of the attachments associated with the document.

    Limits: 2000 characters

    The scope management plan document is created and saved.

View List of Scope Management Plan Documents

Use the Project Properties: Main - Scope Management Plan page to view a list of scope management plan documents, including details such as the document name and the date the document was last updated.

To view this page, open the project and click Scope Management Plan from the Properties content menu.

You can view the following details on this page:

Scope Management Plan Name

Defines the name of this scope management plan document.

Limit: 80 characters

Last Updated Date

Displays the date the document was last updated and saved.

Edit Scope Management Plan Documents

The properties page displays, by default, when you open a document. You can view and edit the fields defined when you first created the document.

See A Guide to the Project Management Body of Knowledge (PMBOK Guide) for more information.

Follow these steps:

  1. Open the project.

    The properties page appears.

  2. Open the scope management plan document.

    The scope management plan properties page appears.

  3. Edit the following field in the General section, and save:
    Scope Management Plan Name

    Defines the name of this scope management plan document.

    Limit: 80 characters

Quality Management Plan Documents

The quality management plan document records the team methods and policy of quality control and its plans to control quality in the project.

Do not submit quality management plan documents for review.

See A Guide to the Project Management Body of Knowledge (PMBOK Guide) for more information.

See the PMI® Compendium of Project Management Practices for more information.

Create Quality Management Plan Documents

Follow these steps:

  1. Open the PMBOK Guide project.

    The project properties page appears.

  2. Open the Properties menu, and click Quality Management Plan.

    The quality management plan properties page appears.

  3. Click New.

    The create quality management plan page appears.

  4. Complete the following fields in the General section:
    Quality Management Plan Name

    Defines the name of this document.

    ID

    Displays the unique identifier for the document.

    Limit: 80 characters

  5. Complete the following fields in the Project Quality System and Quality Management Plan sections, and save:
    Attachment(s)

    Specifies the attachments associated with the document.

    Description of Attachment(s)

    Defines the description of the attachments associated with the document.

    Limits: 2000 characters

    See A Guide to the Project Management Body of Knowledge (PMBOK Guide) for more information.

View List of Quality Management Plan Documents

Use the quality management plan page of project properties to view a list of quality management plan documents. To view this page, open the project and from the Properties menu, click Quality Management Plan.

You can view the following details on the page:

Quality Management Plan Name

Defines the name of this document.

Last Updated Date

Displays the date the document was last updated and saved.

Edit Quality Management Plan Documents

The properties page displays, by default, when you open a document. You can view and edit the fields defined when you first created the document.

Follow these steps:

  1. Open the project.

    The project properties page appears.

  2. Open the Quality Management Plan document.

    The quality management plan properties page appears.

  3. View the following fields in the General section:
    ID

    Displays the unique identifier for the document.

    Limit: 80 characters

    Prepared By

    Displays the name of the resource who created the document.

    Limit: 80 characters

    Last Updated Date

    Displays the date the document was last updated and saved.

  4. Edit the following field in the General section:
    Quality Management Plan Name

    Defines the name of this document.

  5. Edit the remaining fields on the page, and save.

Risk Identification - SWOT Analysis Documents

The risk identification - SWOT analysis document records the project team assessment in terms of strengths, weaknesses, opportunities, and threats.

Risk identification - SWOT analysis documents cannot be submitted for review.

See A Guide to the Project Management Body of Knowledge (PMBOK Guide) for more information.

See the PMI® Compendium of Project Management Practices for more information.

Create Risk Identification - SWOT Analysis Documents

Follow these steps:

  1. Open the PMBOK Guide project.

    The properties page appears.

  2. Open the Properties menu, and click Risk Identification - SWOT Analysis.

    The SWOT analysis page appears.

  3. Click New.

    The create page appears.

  4. Complete the following fields in the General section:
    Name

    Defines the name of this document.

    Limit: 80 characters

    ID

    Displays the unique identifier for the document.

    Limit: 80 characters

  5. Complete the following fields in the SWOT Analysis Report Information section, and save:

    See A Guide to the Project Management Body of Knowledge (PMBOK Guide) for more information.

    The risk identification -SWOT analysis document is saved.

View List of Risk Identification - SWOT Analysis Documents

Use the SWOT analysis page to view a list of risk identification - SWOT analysis documents. To view the page, open the project, and from the Properties menu, click Risk Identification - SWOT Analysis.

The following details display on the page:

SWOT Analysis Report

Defines the name of the document. The value for this field is derived from the Report Name field on the SWOT Analysis properties page.

Last Updated Date

Displays the date the document was last updated and saved.

Edit Risk Identification - SWOT Analysis Documents

The properties page displays, by default, when you open a document. You can view and edit the fields defined when you first created the document.

Follow these steps:

  1. Open the project.

    The properties page appears.

  2. Open the Properties menu, and click Risk Identification - SWOT Analysis.

    The SWOT analysis page lists the risk identification - SWOT analysis documents.

  3. Click the name of the document.

    The SWOT analysis properties page appears.

  4. View and edit the following fields in the General section, and save:
    Report Name

    Defines the name of this document.

    Limit: 80 characters

    ID

    Displays the unique identifier for the document.

    Limit: 80 characters

    Prepared By

    Displays the name of the resource who created the document.

    Limit: 80 characters

    Last Updated Date

    Displays the date the document was last updated and saved.

Project Report Documents

The project report document records the various project statuses, such as scope, schedule, and overall outlook. The report also records plans to address any open issues.

See A Guide to the Project Management Body of Knowledge (PMBOK Guide) for more information.

See the PMI® Compendium of Project Management Practices for more information.

Create Project Report Documents

Create project report documents using the project report page.

Follow these steps:

  1. Open the PMBOK Guide project.

    The properties page appears.

  2. Open the Properties menu, and click Project Report.

    The project report properties page appears.

  3. Click New.

    The create page appears.

  4. Complete the following fields in the General section:
    Report Name

    Defines the name of this project report document. Once you submit the report for review, this field becomes display-only. In management views, the report name is a link to the project report.

    ID

    Displays the unique identifier for the document.

    Limit: 80 characters

  5. Complete the following fields in the Status of Project Relative to Project Objectives section:
    Scope Status

    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:

    • On Scope. The project is on scope.
    • Off Scope. The project is off scope.

    Stoplights:

    • Grey. The project scope status is not defined.
    • Green. The project scope status is "On Scope".
    • Red. The project scope status is "Off Scope".
    Scope Details

    Defines the scope details for the document.

    Limits: 2000 characters

    Schedule Status

    Specifies the schedule status for the project. The value for the field is based on the following checks performed in the order listed:

    • If a project report exists, the value from the Schedule Status field on the project report properties page of the most recent project report document is used.
    • If a project report does not exist but is baselined, the days of delay is calculated by using the difference between the Baseline Finish field on the baseline revision properties page and the Finish Date field on the schedule page of project properties, and the value is used.
    • If a project report exists but not baselined, the days of delay is calculated by using the difference between and the Finish Date field on the schedule page of project properties and the current date, and the value is used.

    Stoplights:

    • White. The project schedule status is not defined.
    • Green. The project is on schedule (no delay).
    • Yellow. The project is less than or equal to 10 days late.
    • Red. The project is more than 10 days late.
    Schedule Details

    Defines the details of the schedule.

    Limits: 2000 characters

    Cost Status

    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:

    • On Budget. The project plan is on budget with the project planned cost.
    • Under Budget. The project plan cost is below the project planned cost.
    • Over Budget. The project plan cost is above the project planned cost.
    Cost Details

    Defines the cost details.

    Limits: 2000 characters

    Quality Status

    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:

    • Excellent. The overall project quality is excellent.
    • Good. The overall project quality is good.
    • Fair. The overall project quality is fair.
    • Poor. The overall project quality is poor.

    Stoplights:

    • Green. The overall project quality is excellent.
    • Yellow. The overall project quality is fair.
    • Red. The overall project quality is poor.
    Quality Details

    Defines the quality details.

    Limits: 2000 characters

    Project Outlook

    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:

    • Excellent. The overall project outlook is excellent.
    • Good. The overall project outlook is good.
    • Fair. The overall project outlook is fair.
    • Poor. The overall project outlook is poor.

    Stoplights:

    • Green. The overall project outlook is good or excellent.
    • Yellow. The overall project outlook is fair.
    • Red. The overall project outlook is poor.
    Project Status Outlook Details

    Defines the details of the project status outlook.

    Limits: 2000 characters

  6. Complete the following fields in the Progress Report section, and save:

    See A Guide to the Project Management Body of Knowledge (PMBOK Guide) for more information.

    The project report document is saved.

View List of Project Report Documents

You can view a list of project report documents using the project report page of project properties. Details include the document name, the date the document was last updated, review status, review completed date, and the number of days the document is in review.

To view the page, open the project, and from the Properties menu, click Project Report.

You can view the following details on the page:

Report Name

Defines the name of this project report document. Once you submit the report for review, this field becomes display-only. In management views, the report name is a link to the project report.

Report Last Updated

Displays the date this project report document was last updated and saved.

Review Status

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:

Review Completed Date

Displays the date the review for this document was completed.

Days in Review

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:

Edit Project Report Documents

The properties page is the default page that displays when you open a document. The fields on this page are defined in the General section when you first created the document. Additional fields also display requiring completion before submitting the document for review.

The fields for the other sections of the document are on separate pages, which you can access from the Properties menu, and edit.

See A Guide to the Project Management Body of Knowledge (PMBOK Guide) for more information.

Follow these steps:

  1. Open the project.

    The properties page appears.

  2. Open the project report document for editing.

    The project report properties page appears.

  3. View the following:
    ID

    Displays the unique identifier for the document.

    Limit: 80 characters

    Prepared By

    Displays the name of the resource who created the document.

    Limit: 80 characters

    Report Last Updated

    Displays the date this project report document was last updated and saved.

    Review Status

    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:

    • New. The document is in draft mode and not submitted for review.
    • Submitted for Review. The document is submitted for review but not reviewed by all reviewers.
    • Review Completed. The document is submitted for review and is reviewed.

    Stoplights:

    • Grey. The document not submitted for review.
    • Green. The document is submitted for review and the review is complete.
    • Yellow. The document is submitted for review but not reviewed.
    Baseline Start

    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.

    Baseline Finish

    Displays the project baseline revision finish date, if a baseline on the project exists. The value for this field is based on the Baseline Finish field on the baseline revision properties page.

    Budget Benefit

    Displays the project planned benefit amount at the time of saving the project report. The value for this field is based on the Planned Benefit field on the budget page of project properties.

    Budget Cost

    Displays the project planned cost amount at the time of saving the project report. The value for this field is based on the Planned Cost field on the budget page of project properties.

    ROI %

    Displays the project planned ROI at the time of saving the project report. The value for this field is based on the Planned ROI field on the budget page of project properties.

    Actual Cost

    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.

    ETC

    Displays the estimate to completion at the time of saving the project report.

    EAC

    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. Assuming, the project continues at the same cost performance index.  EAC uses the following formula:

    EAC = AC + [(BAC - EV) / CPI]
    
  4. Edit the following fields in the General section, and save:
    Report Name

    Defines the name of this project report document. Once you submit the report for review, this field becomes display-only. In management views, the report name is a link to the project report.

Lessons Learned Documents

The lessons learned document records best practices and recommendations for improvements. The aim is to improve project practices for the rest of the project and for future projects.

See A Guide to the Project Management Body of Knowledge (PMBOK Guide) for more information.

See the PMI® Compendium of Project Management Practices for more information.

Create Lessons Learned Documents

Follow these steps:

  1. Open the project.

    The properties page appears.

  2. Open the Properties menu, and click Lessons Learned.

    The lessons learned properties page appears.

  3. Click New.

    The create page appears.

  4. Complete the following fields in the General section:
    Title

    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

    ID

    Displays the unique identifier for the document.

    Limit: 80 characters

  5. Complete the following fields in the Report Information section:
    Lessons Learned Category

    Defines the category for this document. Once you submit this document for review, this field becomes display only.

    Values: Process Change, Framework/ Methodology, Organizational Change, Technology Change, Other, and TBD

    Specific Project Management Process Being Used

    Defines the specific project management process that you are using for this project. Once you submit the document for review, this field becomes display only.

    Limit: 2000 characters

  6. Complete the following fields in the Specific Practice, Tool or Technique Being Used section:

    See A Guide to the Project Management Body of Knowledge (PMBOK Guide) for more information.

  7. Complete the following fields in the Specific Lessons Learned and Recommendations sections:

    See A Guide to the Project Management Body of Knowledge (PMBOK Guide) for more information.

  8. Define the following remaining fields in the Recommendations section, and save:
    Attachment(s)

    Specifies the attachments associated with the document.

    Description of Attachment(s)

    Defines the description of the attachments associated with the document.

    Limits: 2000 characters

    The lessons learned document is created.

View List of Lessons Learned Documents

Use the lessons learned properties page to view a list of lessons learned documents. Details include the document name, the date the document was last updated, the lessons learned category, review status, review completed date, and the number of days the document is in review.

To view this page, open the project, and from the Properties menu, click Lessons Learned.

You can view the following details on the page:

Report

Displays the name of the document. You can click the document name to open the document.

Last Updated Date

Displays the date the document was last updated and saved.

Lessons Learned Category

Defines the category for this document. Once you submit this document for review, this field becomes display only.

Values: Process Change, Framework/ Methodology, Organizational Change, Technology Change, Other, and TBD

Review Status

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:

Edit Lessons Learned Documents

The properties page is the default page that displays when you open a document. The fields on this page are defined in the General section when you first created the document. Additional fields also display requiring completion before submitting the document for review.

The fields for the other sections of the document are on separate pages, which you can access from the Properties menu, and edit.

Follow these steps:

  1. Open the project.

    The properties page appears.

  2. Open the Lessons Learned document.

    The lessons learned properties page appears.

  3. Edit the following fields in the General section, and save:
    Title

    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

    ID

    Displays the unique identifier for the document.

    Limit: 80 characters

    Prepared By

    Displays the name of the resource who created the document.

    Limit: 80 characters

    Last Updated Date

    Displays the date the document was last updated and saved.

    Review Status

    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:

    • New. The document is in draft mode and not submitted for review.
    • Submitted for Review. The document is submitted for review but not reviewed by all reviewers.
    • Review Completed. The document is submitted for review and is reviewed.

    Stoplights:

    • Grey. The document not submitted for review.
    • Green. The document is submitted for review and the review is complete.
    • Yellow. The document is submitted for review but not reviewed.
    Submit for Review

    Specifies to submit this PMBOK Guide project document for review. Select the check box to submit the document for review.

    Default: Cleared

Project Closure Documents

The project closure document reviews all key customer requirements and records that the customer has accepted the project product and deliverables.

See A Guide to the Project Management Body of Knowledge (PMBOK Guide) for more information.

See the PMI® Compendium of Project Management Practices for more information.

Create Project Closure Documents

Follow these steps:

  1. Open the PMBOK Guide project.

    The properties page appears.

  2. Open the Properties menu, and click Project Closure.

    The project closure page appears.

  3. Click New.

    The create page appears.

  4. Complete the following fields in the General section:
    Name

    Defines the name of this document.

    Limit: 80 characters

    ID

    Displays the unique identifier for the document.

    Limit: 80 characters

  5. Complete the following fields in the Project Results section:
    Customer Has Accepted All Project Results

    Defines the list of all the project results.

    Accepted by

    Defines the name of the resource who accepted this document.

  6. Complete the following fields in the All Other Deliverables section:
    Customer Has Accepted All Other Deliverables

    Defines the list of all the project deliverables.

    Accepted by

    Defines the name of the resource who accepted this document.

  7. Complete the following fields in the All Other Project Requirements section:
    Customer Has Accepted All Other Project Requirements

    Defines the a list of all the project requirements.

    Accepted by

    Defines the name of the resource who accepted this document.

  8. Complete the following fields in the Other section, and save:

    See A Guide to the Project Management Body of Knowledge (PMBOK Guide) for more information.

View List of Project Closure Documents

Use the project closure page to view a list of project closure documents. The details include the document name, the date the document was last updated, review status, review completed date, and the number of days the document is in review.

To view this page, open the project, from the Properties menu, and click Project Closure.

You can view the following details on the page:

Report

Displays the name of the document. You can click the document name to open the document.

Last Updated Date

Displays the date the document was last updated and saved.

Review Status

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:

Review Completed Date

Displays the date the review for this document was completed.

Days in Review

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:

Edit Project Closure Documents

Use the project closure page to view a list of project closure documents.

The properties page is the default page that displays when you open a document. It displays the fields that you defined when you first created the document, as well as additional fields you must complete before you submit the document for review. You can edit many of the fields displayed on this page.

Follow these steps:

  1. Open the project.

    The properties page appears.

  2. Open the Properties menu, and click Project Closure.

    The project closure properties page appears displaying a list of project closure documents.

  3. Click the name of the project closure document for editing.

    The project closure properties page appears.

  4. Edit the following fields in the General section:
    Name

    Defines the name of this document.

    Limit: 80 characters

    ID

    Displays the unique identifier for the document.

    Limit: 80 characters

    Checklist Submitted by

    Defines the name of the resource submitting the document.

    Last Updated Date

    Displays the date the document was last updated and saved.

    Review Status

    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:

    • New. The document is in draft mode and not submitted for review.
    • Submitted for Review. The document is submitted for review but not reviewed by all reviewers.
    • Review Completed. The document is submitted for review and is reviewed.

    Stoplights:

    • Grey. The document not submitted for review.
    • Green. The document is submitted for review and the review is complete.
    • Yellow. The document is submitted for review but not reviewed.
    Submit for Review

    Specifies to submit this PMBOK Guide project document for review. Select the check box to submit the document for review.

    Default: Cleared

  5. Edit the fields in the remaining sections, and save.