`

ProjectM Team
Charter

Authors:

Lauren Artz

Carlton Dennis

Nzekwe (Pat) Ibe

Robert King
1. Document Purpose
1.1.The purpose of this charter is to finalize and document the necessary
components for the successful completion of the ProjectM Team Project
required in the Decision Science 261 course offered at The George
Washington University (GWU) during the Fall 2009 semester. This document
will detail the Roles and Responsibilities, Team Communication expectations,
the Performance Objectives and Operational Success criteria, Team
Repercussions, and finally Electronic Signatures to show acceptance of, and
binding to, the provisions of this charter. The ProjectM team members,
having varied experiences, educational backgrounds, physical locations, and
requirements on their times, will use this document to ensure that all team
members fully understand the requirements and expectations of the
ProjectM team. “The Project Charter should be developed in coordination
with stakeholders. As a collaborative effort, establish a solid partnership with
these various stakeholders to help improve project management processes
and on-time, on-budget delivery of projects1.”

2. Roles and Responsibility

2.1.Team Leader – Lauren Artz
2.1.1.Lauren will be responsible for coordinating all team member efforts as
well as contributing to the deliverables.
2.2.Team Members – Carlton Dennis, Pat Ibe, Robert King
2.2.1.Carlton, Pat, and Robert will be primarily responsible for contributions to
the project deliverables.
2.3.Team Contact Information
2.3.1.Lauren Artz
2.3.1.1.Email 1: laurena@gwu.edu
2.3.1.2.Email 2: lauren.e.artz@lmco.com
2.3.1.3.Phone: 817-423-8067 or 682-429-7815
2.3.2.Carlton Dennis
2.3.2.1.Email 1: carlton.dennis@ibx.com
2.3.2.2.Email 2: carlton.dennis@comcast.net
2.3.2.3.Phone: 215-241-9916 or 215-316-9916
2.3.3.Nzekwe “Pat” Ibe
2.3.3.1.Email 1: ibepat@gwmail.gwu.edu
2.3.3.2.Email 2:
2.3.3.3.Phone: +2348053860264
2.3.4.Robert King
2.3.4.1.Email1: rking@gwu.edu
2.3.4.2.Email 2: robert.f1.king@lmco.com
2.3.4.3.Phone: 301.318.4548
 1
"Project Charter Instructions." Texas Project Delivery Framework. State of
Texas, 30 June 2009. Web. 3 Nov. 2009.
<http://www.dir.state.tx.us/pubs/framework/>.

3. Communication Plan

3.1 As distance students team members shall communicate with the team
through email, phone, and the class blackboard group area. Team members
shall use two email addresses for all communications to ensure delivery.
The team prefers those e-mail addresses consist of a personal and work
email.

3.2 Team members shall use the following Microsoft products: Word, Excel, Visio,
Project, and PowerPoint as the primary method of documentation. The team
shall be using the Calibri font for the body of the final project text and the
text size 11 for the entire document.

3.3The team leader is the moderator that keeps the team on topic if discussions
go off topic or team members start talking over each other. Each discussion
shall have an agenda that will be informal and shall be developed as the first
topic of the conference. The agenda will be tracked by Robert King during
the discussions.

3.4The team shall create a schedule of deliverables and deadlines. The team
lead maintains the deliverables list and communicates the schedule on a
weekly basis to all team members. Schedule changes will be reviewed by all
members of the team. The decision to change the schedule will be approved
by majority vote. The team lead has the power to make a decision if time is
of the essence.

3.5The team lead is responsible for final assembly of all team members’ project
deliverables. The final document shall be reviewed by all team members
within a scheduled period of time to be communicated by the team lead.

3.6If team decisions require a vote the team leader will organize vote responses
through e-mail.

3.7The team lead maintains appropriate communication with the Professor to

ensure that the team is current on all assignments and aware of all changes.
The team lead is the primary contact with the Professor and ensures that all
communications are distributed to the team members.

3.8The team objective is a grade of “A” on the final project paper while
presenting a professional document and working effectively as a team.
1. Performance Objectives and Operational Successes

1.1.Due to one team member being physically located 5 time zones ahead of
EST in Nigeria all required teleconferences shall be scheduled to occur no
later than 6pm EST. If a team member has a conflict with the requested
meeting time they shall notify all the team members a minimum of 1 day
prior to the meeting so that the team may attempt to reschedule if
necessary.

1.2.Once a deadline is set for any deliverable, members should submit their
deliverables at least three days prior to the deadline. The team lead
compiles the draft deliverable for review, sends it to all team members for
comment, and subsequently submits any required document to the Professor
or TA.

2. Team Repercussions

2.1.Penalties for failing to meet deliverables per the schedule, the charter, and
team lead requests are listed below. Each team member that digitally signs
the charter below shall agree to the following terms of the project.

2.1.1.First missed teleconference or deliverable deadline results in a warning

to the offending team member. The team member is responsible for
remaining current with information discussed during the missed
teleconference and required to complete the assigned deliverable within
2 business days.
2.1.2.Second missed teleconference or deliverable deadline results in
selection of one following option by the team:
2.1.2.1.Removal of offending team member from team following
discussion with Professor.
2.1.2.2.Requirement to complete additional project deliverables within a
timeframe specific by the team.
2.1.3. A team member who is late to teleconferences by more than 15
minutes without prior warning will have corrective actions as listed in
Section 5.1.2 of this document.

2.1.4.Failure of a team member to respond to more than two emails from the
team lead over a 7 day period shall result in that team member to be
considered removed from the team. The team lead shall notify the
Professor, offending team member, and the remaining team members.

2.2. In the event of friction between team members the entire team shall work to
resolve through discussion with the offending team member. The team lead
shall be responsible for final resolution should the team be unable to come
to consensus.
Approval of the Project Charter indicates an understanding of the purpose
and content described in this deliverable. By signing this deliverable, each
individual agrees work should be initiated on this project and necessary
resources should be committed as described herein.

Approver Name Title Electronic Signature Date

Lauren Artz Team Lead Lauren E. Artz 11/11/09

Nzekwe P.Ibe Team Member Pat Ibe 11/12/09

Robert King Team Member Robert King 12 Nov 09

Carlton Dennis Team Member Carlton Dennis 11/11/09