rs536: duoji: pm 6000 wk 6

RUNNING HEAD: WEEK 3: CHARTER AND SCOPE 2

WEEK 3: CHARTER AND SCOPE 2

Week 3: Project Charter and Scope Assignment

FirstName LastName

Northeastern University

Submitted

In partial fulfillment for

PJM6000 Project Management Practices

Month, Day, Year

Introduction

Include a one to two page written introduction (double spaced, times new roman size 12 font) that outlines the process you utilized to prepare the charter and scope statement. Be sure to cite all sources using APA format as needed. Include a references page as needed after the template.

Remove blue text from cover page, introduction, main body of template, and references pages before you submit. Be sure to turn the ink color for the entire document back to the “black” color and font style to “not italicized” before submitting. Remove any unused rows from tables in the main template (do not have blank rows). Overall, before submitting, consider: would you submit this project charter to your boss or your project sponsor? If not, then make adjustments to this document before submitting…

Project Charter

Project Name: (Insert project name here)

Project Manager: (Insert your name here)

Executive Summary

Include a concise overview here (about a paragraph or two) that addresses the following:

Where did this project come from?

Why is it being done?

What impact will the project create (internally, externally)?

What strategic plan does it contribute to?

What does the customer receive/not receive by project end?

What key assumptions are driving this project?

What risks could challenge project success?

Goals

What business/organization goal(s) does this project support?

What business need is being satisfied by this project?

Objectives

What, specifically, needs to be done to meet project/customer requirements/expectations/goal(s)?

What is the target of the project?

Note: Ensure each objective contributes to the goal. Check to satisfy the "SMART" criteria

Scope:

The following work is considered in scope and out of scope for this project:

Work Includes	Work does not Include
· Add as many rows as needed to specify work included as part of this project.	· Add as many rows as needed to specify work NOT included as part of this project; you may need to make some assumptions. Be sure to note assumptions.
·	·
·	·
·	·

Phases ⁄ Deliverables:

What are the major components of work to meet the goals/objectives/scope?

What are the high level customer, process, and project deliverables within each phase?

Phase	Description of Phase	Deliverables
		Internal	External
e.g. Initiation	Short description here	·	·
		·	·
		·	·
		·	·

Assumptions:

List any assumptions you made when creating the charter

Assumption	Rationale	Probability of Assumption being True	Impact to Project if Assumption is True
Short description of assumption	Why is this a reasonable assumption?	High, medium, low	High, medium, low

Risks:

What events could jeopardize this project's success?

Risk	Probability of Risk Occurring	Impact if Risk Occurs
Short description of risk	High, medium, low	High, medium, low

Constraints:

What is restricting this project?

What standards, regulations, technologies, resource availability might impact this project?

Constraint	Impact of constraint
Short description of constraint	How might the constraint impact the project? How large is the constraint?

Preliminary Budget:

Include a short summary of the anticipated budget (costs) for this project. Your case study contains some of the numbers you need. Some considerations to include are:

What are the estimated costs to complete this project (document variability, range, precision at this point)

What is the financial justification for this project? (i.e. Benefit Cost Analysis, Return on Investment, NPV . . .)

What financial gains are there to doing/not doing this project?

High Level Schedule:

When are the phases/deliverables planned to begin/end?

Phase and/or Deliverable	Anticipated Timeline

Milestones:

What major points are important to communicate/measure against?

When should/will they occur?

Use the Scope, Phase Deliverables, and High Level Schedule sections above to help inform what should be listed in this section.

Resource Requirements:

Sometimes projects require people with special skills and/or knowledge. These folks can be constraints if not available. What specialized person(s) are necessary to complete this project?

Team Member	Role	Responsibility
	Sponsor
	Project Manager

Management Approaches:

Provide a very high-level overview of how communication will take place for your project. This is high-level, as each plan below will be its own document/template (which you’ll learn how to create in future courses). An example is included in the first row of the table. Some considerations include:

How will status be documented and communicated?

How will change be managed?

How will issues be escalated?

How will the risk be managed?

Communication Type	Audience	Frequency	Agenda/ Content	Responsible	Distribution Media
Status report	All stakeholders	Weekly	Update of project status	Project Manager	Email

Sign-offs/Reviews:

At what points will management/customer/team/peer reviews be conducted? For what purpose?

Who signs off on the project reviews?

Role	Name(s) of person(s) (if known)	Item(s) to sign-off
Sponsor	If you know the name of this person – from the case study – include here. Otherwise, state “to be identified	List the types of documents/approvals that this person will be signing-off on, such as “Project Charter, Project Budget, Timelines, Phase Deliverables, etc.”
List other roles here, one role per row. Insert as many rows as you feel appropriate.

Acceptance Criteria:

What measurements will be used to determine customer acceptance?

What performance criteria define project success (i.e. time, cost, resource, quality prioritization)?

Acceptance Criteria	Priority	Responsible to Accept/Sign-Off
Short description here, such as “project delivered on budget” or “project delivered on time”	High, medium, low	Who is going to “sign for acceptance for this criteria?

Impacted ⁄ Interdependent Projects

It is not unusual for one project to impact (or be impacted by) other project(s). We want to bring visibility to those projects here.

What projects connect to this project via inputs/outputs?

What products are impacted by this project/how?

What other projects are addressing related issues?

Project	Interdependency Relationship

References

(The generic reference format is):

Last Name, F. M. (Year). Article title. Journal Title, Volume(Issue), page numbers.

Last Name, F. M. (Year). Book title. City Name, State: Publisher Name.

(An example appropriate example citation for the PMBOK would be as follows; notice the “reverse indentation” of the second and remaining lines of the citation):

Project Management Institute. (2017). A guide to the project management body of knowledge (PMBOK guide) (6th. ed.). Newtown Square, Pa: Project Management Institute.

Note:

1. The information in this template has been adapted from the following resources:

Purdue Online Writing Lab (OWL). (n.d.). Annotated bibliography samples. Retrieved from https://owl.english.purdue.edu/owl/resource/614/03/

2. Delete all blue text from this page and insert your own text.