Posted: June 13th, 2015

TECH 6362 Project Charter Peer Review Template

TECH 6362 Project Charter Peer Review Template

Peer Reviews Completed By: (YourName)

First Review For: (StudentName)

Title Page and Table of Contents
Does the document include a professional title page with the and a table of contents?
Comment:

Project Statement
Provide a one or two line description that includes the project’s main objective, high-level cost estimate, and time estimate.
Comment:

Business Drivers/Background
Describe the reasons for recommending the project, including background information, business problem, etc.
Comment:

Vision
The idealistic view of what business will be like after the project is completed.
Comment:

Goal Statement
A high-level statement that provides the overall context for what the project is trying to accomplish.
Comment:

Objectives
Describe specific, measurable, attainable, realistic, time-bound, concrete objectives for achieving the goal.
Comment:

Scope
Stated assumptions about limitation related to resources, time, or scope. This includes items that must be within the scope and items that are outside the scope of the project. For example, the project does not include training.
Comment:

Schedule
Include Phases and Milestones
Milestones should be worded as binary events in the past tense. They are not worded as ongoing activities. They are worded such that they can be used to measure progress toward the creation of deliverables. They should mark major events in the project’s lifecycle. Typical milestones are use cases completed, scope statement accepted, WBS approved, etc. They will often include steps that are part of the planning process.

Comment:

Cost Projection
The total estimated cost of the project.
Comment:

High Level Deliverables
This is a table of tangible, verifiable outcomes of work that satisfy the project objectives. Ideally, deliverables are components of the final deliverable or the products needed to produce final product or service. Unlike milestones, these are not events and they will consume resources. Typical deliverables are reports, lists, code modules, website forms, etc.
Comment:

Project Organization
Roles & Responsibilities
Roles and responsibilities assigned to each individual or group resource to the project.
Governance
Describes the oversight committees, jurisdictional management groups and any other required approvals
Team Composition
Org chart or matrix identifying all human resources allocated to the project, their reporting relationships and % of time allocated to the project

Comment:

Approach
Description of how the project will accomplish its goals. Will the project be composed of multiple phases?

Comment:

Assumptions and Constraints
Assumptions:
The events that need to occur for the project to be successful but are outside the total control of the team.

Constraints:
Limitations generally outside the control of the project, which might negatively affect the project scope

Comment:

Performance Measures/Outcomes
Describe predetermined methods for assessing if the project has achieved its goals.

Comment:

Acceptance
This is a table identifying the major stakeholders, titles, and a place to record each person’s signature.
Comment:

Second Review For: (StudentName)

Title Page and Table of Contents
Does the document include a professional title page with the and a table of contents?
Comment:

Project Statement
Provide a one or two line description that includes the project’s main objective, high-level cost estimate, and time estimate.
Comment:

Business Drivers/Background
Describe the reasons for recommending the project, including background information, business problem, etc.
Comment:

Vision
The idealistic view of what business will be like after the project is completed.
Comment:

Goal Statement
A high-level statement that provides the overall context for what the project is trying to accomplish.
Comment:

Objectives
Describe specific, measurable, attainable, realistic, time-bound, concrete objectives for achieving the goal.
Comment:

Scope
Stated assumptions about limitation related to resources, time, or scope. This includes items that must be within the scope and items that are outside the scope of the project. For example, the project does not include training.
Comment:

Schedule
Include Phases and Milestones
Milestones should be worded as binary events in the past tense. They are not worded as ongoing activities. They are worded such that they can be used to measure progress toward the creation of deliverables. They should mark major events in the project’s lifecycle. Typical milestones are use cases completed, scope statement accepted, WBS approved, etc. They will often include steps that are part of the planning process.

Comment:

Cost Projection
The total estimated cost of the project.
Comment:

High Level Deliverables
This is a table of tangible, verifiable outcomes of work that satisfy the project objectives. Ideally, deliverables are components of the final deliverable or the products needed to produce final product or service. Unlike milestones, these are not events and they will consume resources. Typical deliverables are reports, lists, code modules, website forms, etc.
Comment:

Project Organization
Roles & Responsibilities
Roles and responsibilities assigned to each individual or group resource to the project.
Governance
Describes the oversight committees, jurisdictional management groups and any other required approvals
Team Composition
Org chart or matrix identifying all human resources allocated to the project, their reporting relationships and % of time allocated to the project

Comment:

Approach
Description of how the project will accomplish its goals. Will the project be composed of multiple phases?

Comment:

Assumptions and Constraints
Assumptions:
The events that need to occur for the project to be successful but are outside the total control of the team.

Constraints:
Limitations generally outside the control of the project, which might negatively affect the project scope

Comment:

Performance Measures/Outcomes
Describe predetermined methods for assessing if the project has achieved its goals.

Comment:

Acceptance
This is a table identifying the major stakeholders, titles, and a place to record each person’s signature.
Comment: