Topic:Project Report
Subject:Project management
Volume: 3 pages
format: APA
Type: Essay
Description
It should be written as if it were a formal progress report for senior management. It should include the following information: completed performance template, updated scope statement, Gantt chart in MS Project (include your WBS), probability/impact matrix with at least 10 potential risks for the project, summary or sample of completed deliverables that are being executed, feedback from client. (if you are completing the project with a partner or small group, each person must upload the report. The report can be completed jointly and the same for all participants).
Risk Management Plan
Date
Project Name:
1. Methodology
2. Roles and Responsibilities
3. Budget and Schedule
4. Risk Categories
5. Risk Probability and Impact
6. Risk Documentation
Quality Management Plan
Date
Project Name:
Introduction
Quality Standards
Metrics
Problem Reporting and Corrective Action Process
Supplier Quality and Control
Note to the Author
[This document is a template of a Requirements Management Plan Template document for a project. The template includes instructions to the author, boilerplate text, and fields that should be replaced with the values specific to the project.
• Blue italicized text enclosed in square brackets ([text]) provides instructions to the document author, or describes the intent, assumptions and context for content included in this document.
• Blue italicized text enclosed in angle brackets (<text>) indicates a field that should be replaced with information specific to a particular project.
• Text and tables in black are provided as boilerplate examples of wording and formats that may be used or modified as appropriate to a specific project. These are offered only as suggestions to assist in developing project documents; they are not mandatory formats.
When using this template for your project document, it is recommended that you follow these steps:
1. Replace all text enclosed in angle brackets (i.e., <Project Name>) with the correct field values. These angle brackets appear in both the body of the document and in headers and footers. To customize fields in Microsoft Word (which display a gray background when selected):
a. Select File>Properties>Summary and fill in the Title field with the Document Name and the Subject field with the Project Name.
b. Select File>Properties>Custom and fill in the Last Modified, Status, and Version fields with the appropriate information for this document.
c. After you click OK to close the dialog box, update the fields throughout the document with these values by selecting Edit>Select All (or Ctrl-A) and pressing F9. Or you can update an individual field by clicking on it and pressing F9. This must be done separately for Headers and Footers.
2. Modify boilerplate text as appropriate to the specific project.
3. To add any new sections to the document, ensure that the appropriate header and body text styles are maintained. Styles used for the Section Headings are Heading 1, Heading 2 and Heading 3. Style used for boilerplate text is Body Text.
4. To update the Table of Contents, right-click and select “Update field” and choose the option- “Update entire table”
5. Before submission of the first draft of this document, delete this “Notes to the Author” page and all instructions to the author, which appear throughout the document as blue italicized text enclosed in square brackets.]
INTRODUCTION
1.1 PURPOSE OF THE REQUIREMENTS MANAGEMENT PLAN
[Provide the purpose of the Requirements Management Plan. This document should be tailored to fit a particular project’s needs.]
The Requirements Management plan is used to document the necessary information required to effectively manage project requirements from definition, through traceability, to delivery.
The Requirements Management Plan is created during the Planning Phase of the project. Its intended audience is the project manager, project team, project sponsor and any senior leaders whose support is needed to carry out the plan.
2 REQUIREMENTS MANAGEMENT OVERVIEW
2.1 ORGANIZATION, RESPONSIBILITIES, AND INTERFACES
[Describe here who is going to be responsible for performing the various activities described in the requirements workflows defined later in this document.]
2.2 TOOLS, ENVIRONMENT, AND INFRASTRUCTURE
[Describe the computing environment and software tools to be used in fulfilling the Requirements Management functions throughout the project or product lifecycle.
Describe the tools and procedures that will be used to control the versioning of the Requirements items generated throughout the project or product lifecycle.]
3 REQUIREMENTS MANAGEMENT
3.1 ASSUMPTIONS/CONSTRAINTS
[Define any assumptions and/or constraints taken into account when defining requirement for this section of this document.]
3.2 REQUIREMENTS DEFINITION
[Describe the approach and tools that the project will use to define the specifications of the project requirements. Explicitly describing project requirements promotes the correct and efficient development and delivery of that requirement. Appendix C is for a Requirements Definition Log that the project team can adapt and populate for this purpose. (Use the CDC UP Requirements Definition Practices Guide as reference to complete this section.)]
3.3 REQUIREMENTS TRACEABILITY
[Describe the approach and tools that the project will use to trace the project requirements throughout the systems life cycle. The approach that is followed should enable the project team to ensure that the project delivers the project requirements exactly as specified and that they fulfill the project requirements. Appendix D is for a Requirements Traceability Matrix that the project team can adapt and populate for this purpose. (Use the CDC UP Requirements Traceability Practices Guide as reference to complete this section.)]
3.4 WORKFLOWS AND ACTIVITIES
[Describe the workflows and activities that apply to managing requirements. Describe review activities, including review objectives, responsibilities, timing, and procedures.]
3.5 CHANGE MANAGEMENT
[Describe the process by which problems and changes are submitted, reviewed, and resolved. This should include the process for negotiating requirements changes with customers, and any contractual processes, activities, and constraints.
Describe the membership of the Change Control Board (CCB) and procedures for processing change requests and approvals to be followed by the CCB.]
Requirements Management Plan Approval
The undersigned acknowledge they have reviewed the <Project Name> Requirements Management Plan and agree with the approach it presents. Changes to this Requirements Management Plan will be coordinated with and approved by the undersigned or their designated representatives.
[List the individuals whose signatures are required. Examples of such individuals are Project Sponsor, Business Steward, Technical Steward and Project Manager. Add additional signature lines as necessary.]
Signature: Date:
Print Name:
Title:
Role:
Signature: Date:
Print Name:
Title:
Role:
Signature: Date:
Print Name:
Title:
Role:
