|
No.
|
Document File Name
|
Document Content or Purpose
|
|
|
|
|
1
|
Budget Review Agenda and Checklist.docx
|
Agenda with specific topics to be covered with suggested time allocation for each topic.
|
|
2
|
Initiation Review Agenda and Checklist.docx
|
Agenda with specific topics to be covered with suggested time allocation for each topic.
|
|
3
|
Project Archive Checklist.doc
|
Project archives contain all final project deliverables, communications materials, procurement-related documents, and project management deliverables. What follows is a checklist to aid in compiling a project archive.
|
|
4
|
Project Plan Review Agenda and Checklist.docx
|
Agenda with specific topics to be covered with suggested time allocation for each topic.
|
|
5
|
Requirements Review Agenda and Checklist.docx
|
Agenda with specific topics to be covered with suggested time allocation for each topic.
|
|
6
|
Schedule Review Agenda and Checklist.docx
|
Agenda with specific topics to be covered with suggested time allocation for each topic.
|
|
7
|
Scope Review Agenda and Checklist.docx
|
Agenda with specific topics to be covered with suggested time allocation for each topic.
|
|
8
|
Execution Process Kick Off Meeting Agenda.docx
|
Agenda with specific topics to be covered with suggested time allocation for each topic.
|
|
9
|
Initiation Process Kick Off Meeting Agenda.docx
|
Agenda with specific topics to be covered with suggested time allocation for each topic.
|
|
10
|
Origination Process Kick Off Meeting Agenda.docx
|
Agenda with specific topics to be covered with suggested time allocation for each topic.
|
|
11
|
Planning Process Kick Off Meeting Agenda.docx
|
Agenda with specific topics to be covered with suggested time allocation for each topic.
|
|
12
|
Weekly Project Status Meeting Agenda.docx
|
Agenda with specific topics to be covered with suggested time allocation for each topic.
|
|
|
|
|
13
|
Communications Management Plan.docx
|
The Communications Management Plan outlines the procedures and policies that govern how and when project team members and stakeholders receive information regarding the project. It includes the format, content and frequency of the communications, and who is responsible for the communication.
|
|
14
|
Configuration Management Plan.docx
|
The Project Configuration Management Plan addresses two elements of change management. The first is change management for the product or system being built. The second aspect of change management addresses changes to the project management documents and how changes are identified, analyzed, approved and implemented.
|
|
15
|
Cost Management Plan.docx
|
The Cost Management Plan includes the Project Budget, funding approval requirements, identifies how costs will be tracked and reported, and how changes to the Project Budget will be approved and communicated.
|
|
16
|
Procurement Management Plan.docx
|
The Procurement Management Plan describes what products or services will be procured for the project. It describes how such products or services will be procured, and who is involved in the process.
|
|
17
|
Project Human Resources Plan.doc
|
The Human Resource Management Plan identifies and documents the resource requirements for the project, including specialized skills, and roles and responsibilities. The resources for the project are identified and documented in a project organization chart and team roster. Reporting relationships are defined. Team assignments are documented. Project team development (education) requirements are documented (if applicable), as well as the Project Manager’s approach to developing a cohesive team environment.
|
|
18
|
Project Issue Management Plan.doc
|
Issue Management Plan outlines the issue management approach for the project. It provides standard terminology, clear roles and responsibilities, a detailed description of the approved issue management process, and the standard templates used in that process. It is designed to guide the project team and stakeholders.
|
|
19
|
Project Management Plan.doc
|
The project management plan is an overarching document that describes the processes that will be used to plan, execute, monitor and control, and close the project. The project management plan, depending upon the scope and complexity of the project may not contain plans for all project management processes
|
|
20
|
Quality Management Plan.doc
|
The Quality Management Plan addresses the Quality Assurance and Quality Control processes that will be employed on the project. The Quality Management Plan addresses two components of quality, the quality of the project management processes, and the quality measurements of the system, product or service being produced.
|
|
21
|
Requirements Management Plan.doc
|
Requirements Management Plan describes the processes for how requirements will be analyzed, documented and managed throughout the project. Document the change control procedures to be followed and who must approve requirements changes. Describe how the requirements will be collected, analyzed, and documented. Describe the configuration management activities and how changes to the product, service or results requirements will be initiated, analyzed, traced, tracked and approved.
|
|
22
|
Risk Management Plan.docx
|
The Risk Management Plan identifies internal or external conditions or events that can have an impact on project quality, cost or schedule. Risks are evaluated and assigned priorities. Risk response strategies are developed for high priority risks.
|
|
23
|
Schedule Management Plan.docx
|
The Schedule Management Plan encompasses the development of the initial project schedule. It documents the scheduling or estimating methodologies, scheduling tool, and criteria for monitoring and controlling the project schedule. Once approved, the project schedule forms the baseline against which future performance will be measured.
|
|
24
|
Scope Management Plan.doc
|
The project scope definition includes many processes that further define the boundaries and exclusions of the project, and the work to be performed. It includes further development of the high level product and project requirements. A Scope Management Plan is established to describe how the project scope will be documented, verified and controlled. Product and project deliverables are defined and acceptance criteria is documented. The project scope definition process begins in the planning stages of the project, and is revisited in later phases of a project.
|
|
|
|
|
25
|
Deliverable Acceptance Criteria.docx
|
List of Deliverables - describe the Criteria that must be met in order for the deliverable to be considered acceptable or approve the deliverable.
|
|
26
|
Deliverable Acceptance Form.doc
|
For each deliverable being presented, describe the Criteria that must be met in order for the deliverable to be considered acceptable at the stage at which the review is taking place. A deliverable may have many reviews over the different project phases.
|
|
27
|
Evaluation Model Requirements List Template.doc
|
Requirements list with a weighting factor.
|
|
28
|
Phase End Review Report.docx
|
This report will be completed by the Project Manager following the Phase end review and filed in the project repository
|
|
29
|
Product Requirements.docx
|
Documenting the requirements of the Product that is to be delivered as a result of the project.
|
|
30
|
Project Budget.xlsx
|
Sample Project Budget worksheet that includes Labor, Material, Travel and other items.
|
|
31
|
Project Business Case.doc
|
The business case documents the business opportunity or problem that the proposed project will address. The business case development process involves analyzing and documenting various aspects of the project, including alternative approaches, and financial impacts. It provides the information necessary to compare competing projects with one another, and to make a decision about whether a project should proceed.
|
|
32
|
Project Charter.doc
|
The Project Charter is a high level document that, once approved, authorizes the Project Manager to engage resources to begin the planning processes for the project. The Charter can be thought of as an Executive Summary of the project, and is usually only two-to three pages long. It summarizes information from the Project Business Case, describes the high level requirements of the project, identifies Project Stakeholders for subsequent phase of the project, and describes the governance processes and authority levels for the project.
|
|
33
|
Project Issue Log.docx
|
Log of Project Issues
|
|
34
|
Project Requirements.docx
|
Includes Project Governance, Management, and Delivery Requirements along with the assumptions.
|
|
35
|
Project Stakeholder Management Strategy.docx
|
Potential Strategies (for gaining support or reducing obstacles)
|
|
36
|
Project Stakeholder Register.docx
|
Includes Project Roles, Expectations and Influence areas
|
|
37
|
Project Status Report.DOC
|
Summarize the project’s Status. This section should be brief, presenting a few major accomplishments or possibly a critical issue.
|
|
38
|
Project Team Roster template.doc
|
Team Roster with Role, Organization and Contact information.
|
|
39
|
References Response Form Template.doc
|
Customer response form for products that are being considered by the project.
|
|
40
|
Requirements Traceability Matrix.docx
|
Includes identification of the requirements, its owner, priority and other details.
|
|
41
|
Risk Evaluation Worksheet.xlsx
|
Documents the Risks, its probability of occurrence, impact and mitigation approaches.
|
|
42
|
Vendor Cost Estimate Template.doc
|
Compilation of total costs for product, maintenance, support, training to help develop the Total Cost of Ownership.
|
|
43
|
Vendor Response Form Template.docx
|
A detailed Vendor Response Form that will ensure that information that is required before purchasing the product is as complete as possible. This will help remove surprises later.
|
|
44
|
WBS Sample Organization.pptx
|
Sample WBS Structure in PowerPoint
|
|
45
|
WBS Sample project plan.mpp
|
Sample Project WBS in Microsoft Project
|
|
|
|
|
46
|
Creating an RFP and RFI.doc
|
A guide to preparing a RFP or an RFI including tools and techniques to be used.
|
|
47
|
Feasibility and Cost-Benefit Analysis.doc
|
These guidelines concern feasibility and cost benefit analysis. Good solutions require thorough evaluation of alternatives before recommending change. This document describes how to analyze and document those alternatives on the basis of four feasibility criteria: operational, technical, schedule and economic.
|
|
48
|
Glossary of Tools and Techniques.docx
|
Glossary of Project Management Tools and Techniques and Terms
|
|
49
|
Interviewing Techniques and Procedures.doc
|
A guide to Interviewing techniques: setting up objectives, structure and developing a questionnaire and conducting an interview
|
|
50
|
Refining a Project Methodology.doc
|
This document discusses the process of selecting a development methodology that is appropriate to a project, and creating a version of that methodology tailored to the project, both in scope or size and in content.
|
|
51
|
Requirements Gathering using JAD.docx
|
The techniques in this document involve collaboration between process developers and users for the purpose of making a lot of progress in a short time. Specific focus is on Facilitated sessions, Joint Application Design (JAD) and Joint Requirements Planning (JRP)
|
|
52
|
Review and Approval Guidelines.doc
|
This guideline contains details about several types of reviews and how to conduct those reviews and approvals. These include: Data Modeling, Process Model, Team Reviews, Design Reviews, Quality Reviews and Conducting Confirmations and Signoffs.
|