Part I: Team Charter

Course PMG 422 28853

Instructor Dr. K

❚ Team Member Information

State (or
Name ASU Email Address country, if Phone (optional)
outside U.S.)
Kevin Miranda kjmiran1@asu.edu WA (323) 271-8540
Joshua Moody jdmoody2@asu.edu TX (520) 425-6294
Triston Miller Tcmill10@asu.edu NC (980) 431-8458
Alexis Moore amoore88@asu.edu AZ (916) 298-9319

❚ Purpose Statement and Team Objectives

This team has been formed to complete the Culminating Team Project Milestone for PMG 422
Class 28853. Our overall goal is to master the course material to the best of our abilities and
demonstrate those skills through this Culminating Team Project Milestone. We are committed to
working as a team by monitoring our progress, effectiveness, and follow through on
commitments made to this team and this class.

❚ Analysis of Strengths and Developmental Needs

Skills, characteristics, and/or knowledge individual members can contribute (list by team
member):

Here we will determine a common set of performance goals through the analysis of the skill sets
of all team members in relation to the work we have to complete. We identify our background
experience and complimentary skills.

Strengths:

Kevin Miranda: I have good communication skills, I like to finish things early for review, I am
fairly good with computers, and I can easily learn how to produce visual products. I have
experience with managing large groups of people. I am a problem solver.

Joshua Moody: I am very detail oriented with a keen eye for reviewing documents for accuracy.
I communicate well and I have experience proving adaptable and efficient as it relates to
working with different personalities, character traits, and work ethics within a group setting.

Triston Miller: I am good with time management and ensuring I have enough time to complete
my assignments prior to any deadlines so that I can review the work to look for any errors or
areas that need improvement. I have a lot of experience working in groups as I do this often at
my job and have worked on several group projects here at ASU.

Alexis Moore: I’m a very people-oriented person, and I work best when someone applies
pressure to me, but I can apply pressure to myself just fine. My talents involve editing,
reviewing, and proofreading, and ensuring that written works flow well. I’ve worked in group
projects before for my schooling, but I have no professional experience.

Development Needs:

❚ Functional Roles

Project Lead - They will oversee the entire project and determine goals with input from the rest of the
team. They will proactively research the requirements of each project, develop goals and tasks for each
project to present them in the meetings. They will initiate feedback from each team member and facilitate
collaborations and accountability.

Editor - They will compile inputs from each team member to produce artifacts for submission for each
milestone. They will collaborate primarily with the Project Manager and with the team members on
information, format, and delivery.

Team Member - Each team member will provide input on what tasks, goals and requirements they feel
confident in executing. They will complete tasks and deliverables assigned to them by the agreed
deadlines. They will provide clear communication to the rest of the team on their progress. Each team
member will provide feedback on the final version of each artifact.

Project Lead: Kevin Miranda

Editor: Joshua Moody
Team Member: Triston Miller
Team Member: Alexis Moore

❚ Team Due Dates & Project Timeline

Milestone 1:

Individual Contributions:

**March 28, 2024 @ 11:59 PM Arizona Time**

Final Version by Project Lead & Editor:

**March 29, 2024 @ 11:59 PM Arizona Time**

Final Version Approval & Corrections by all Team Members:

 **March 30, 2024 @ 12:00 PM Arizona Time**

Final Version Submission by Team Leader:

**March 31, 2024 @ 12:00 PM Arizona Time**

Milestone 2:

Individual Contributions:

**April 11, 2024 @ 11:59 PM Arizona Time**

Final Version by Project Lead & Editor:

**April 12, 2024 @ 11:59 PM Arizona Time**

Final Version Approval & Corrections by all Team Members:

**April 13, 2024 @ 12:00 PM Arizona Time**

Final Version Submission by Team Leader:

**April 14, 2024 @ 12:00 PM Arizona Time**

Milestone 3:

Individual Contributions:

**April 20, 2024 @ 11:59 PM Arizona Time**

Final Version by Project Lead & Editor:

**April 21, 2024 @ 11:59 PM Arizona Time**

Final Version Approval & Corrections by all Team Members:

**April 22, 2024 @ 12:00 PM Arizona Time**

Final Version Submission by Team Leader:

**April 23, 2024 @ 12:00 PM Arizona Time**

❚ Team Process Management

Team Meetings:

We will hold each meeting every Monday at 6 PM Arizona time.

● Purpose of the Meeting: To synchronize information to the whole team. Identity

deliverables and assign tasks to each member.
● Agenda: We identify what steps need to be taken to produce project deliverables. We
identify who is responsible for what deliverable. We update the team on the progress of
each deliverable. We also discuss any potential issues or setbacks.
● Meetings Notes: After each meeting, notes will be posted in the Discord server
summarizing topics discussed and what team members are assigned.
● Code of Conduct:
○ Arrive on time.
○ Stick to the agenda.
○ One person speaks at a time.

Ground Rules:

● Discord is our primary communication and where each meeting will take place.
● Only voice is required at the meeting. Video is optional.
● If a team member misses the meeting, they must check in with the Discord server each
week by Tuesday night to see their assigned work.
● A check in just means acknowledging to the team in a message on the server that you
have synced with the information provided.
● The Project Leader will contact those who have not checked in after Tuesday to get some
acknowledgement. If the absent team member does not respond by Thursday, 6 pm
Arizona time, of that same week, the team will discuss whether they divide the work,
assigned to the absentee member, amongst themselves and contact the professor about the
student. If the team decides the absentee member has not contributed without a good
reason, the Team Leader will contact the instructor for mitigation.
● ALL ASSIGNED WORK IS DUE THE THURSDAY NIGHT 11:59 PM ARIZONA
TIME BEFORE THE DEADLINE.
● The Editor has all day FRIDAY to compile the work into a final version with the help of
the Project Lead.
● The team has until 12pm on the Saturday before the deadline to approve/disapprove the
final version for submission. Reasoning: To have time the rest of Saturday and Sunday
for the team to rework any portions of the assignment.

Decision Making Procedure:

The team will vote on approval of final submission by the deadline set in the Ground Rules
portion of the Team Charter. An approval vote of 4 out of 5 members by the set deadline will be
the agreed upon requirement to move forward with the submission of the team’s work. Feedback
is encouraged and members must generate alternative solutions before the deadline for approval.
Team Communication:

Discord will be the primary form of communication. If a member does not respond on Discord,
any team member is allowed to email that member to their provided email. Each team member
has the option to provide their personal cell phone number, but it is not a requirement. The phone
number is only to be used by the Team Leader to contact the absentee team member as a final
attempt in communication before the team progresses to involve the instructor.

Expectations of Team Members:

Attendance at meetings:
Attendance is expected at every meeting. If a member is absent, they must communicate their
absence in a timely manner and follow up with the team as soon as possible.

Participation:
Full participation is expected of all team members. If someone feels that others are not
contributing enough, the concerned member will bring it up with the Team Leader or in the
meetings if they choose.

General Courtesy and Respect:

Members will respect each team member under the guidance of the Arizona State University
Student Code of Conduct, the Syllabus for PMG 422 28853, and the Grading Policy by the
instructor posted on the announcements section in Canvas titled “PMG 422 TEAM PROJECT”
 Part II: Overview of Project Quality
Management

The Role of Quality in Project Management

Project Quality management can be defined as a multitude of processes and functions

within project management that help ensure the project is delivering on all the quality
expectations set by the stakeholder at the onset of the project. In the textbook, Project Quality
Management by Kenneth Rose, the author discusses multiple elements that go into project
quality management such as quality planning, quality assurance quality control and quality
improvement (Rose, 2014, pg. 49). Each of these elements cover multiple phases of project
quality management and help ensure that every aspect of a project that impacts quality is
covered. For example, quality planning ensures that the schedule set forth by the Project
Manager allows for the work packages to be completed in a timely manner with sufficient time
set aside for review and corrections as needed. Quality assurance in a project enables a project
team to compare the work they have completed to the expectations of the stakeholder and ensure
that the finished work aligns with or exceeds those expectations. Quality control relates to the
first two aspects of the quality management elements in terms of how quality control consists of
testing and inspecting the work that has already been done and ensuring that the project is still on
schedule to be delivered within the established timeframe set forth during the quality planning
phase. Lastly, quality improvement ensures that the project manager and team are continuously
identifying and/or updating methods and processes of improvement regarding the overall quality
of the project.

The Role of Management in Development of Project Quality Management (PQM) Practices

Project quality management is a process that entails the assurance of a project meeting
both organizational and stakeholder standards (Rose, 2014, pg. 49). To ensure a project meets
project quality standards, it must capitalize on the three constraints of time, cost, and scope. This
means that a quality deliverable is on time or early, meets or is under budget, and meets the
requirements within the scope of work. Each organization has different standards for quality,
therefor additional requirements may be present depending on the circumstances. The
significance of project quality management is that the effects of quality management do not end
with the conclusion of a project. If the project closes with a high-quality deliverable, and the
relationship between stakeholders and project managers has been well managed, then both the
project manager and organization gain good credibility as a trustworthy entity that can deliver
quality products. This extends past the area of credibility, and into other areas such as making
good faith contracts, and the consideration of how ethical a project may be. If an organization is
known for delivering quality products, it adds a layer of trust to a contract, that the managers
behind the project will do their best to always ensure a quality product. The same applies to
ethics and morals as well, a project that is high quality should also be applying to moral
standards as well. When a quality product is morally correct in its production, then there is the
added benefit of good ethics.

Six (6) Key Attributes of Project Quality Management

Quality planning is a preventative measure established to identify quality requirements or

standards for a given project and its deliverables (Rose, 2014, pg. 50). Quality is something that
should be planned for as opposed to inspected and corrected, thus conserving financial and
human resources. Quality assurance is an element of quality management aimed at providing
“assurance” that quality requirements set forth will be adhered to, and/or exceeded (Rose, 2014,
pg. 27). This generally involves developing a quality assurance plan that implements pre-defined
metrics that are specific and measurable, as well as data collection methods, and assigns
responsibilities. Quality control is focused on monitoring and documenting results of project
outputs to ensure they meet customer standards, and/or determine corrective action if not (Rose,
2014, pg. 83). Quality improvement, can be thought of as a process that uses data to continuously
improve performance levels, thereby theoretically improving organizational processes and policy
in relation to quality.
Communication is an important aspect of project management and any task or job that
requires collaboration. In Project Quality Management by Kenneth Rose, the author discusses
how communication is vital and this aspect stretches beyond just within the project team itself
and how communication with outside sources such as customers, suppliers and stakeholders is
essential to ensuring the quality of the project (Rose, 2014, pg. 27). Risk management and
quality are directly related in project management. The possibility of risks occurring in a project
remain high and it’s important to take steps to ensure these risks don’t negatively impact the
quality of the project. In The Handbook of Program Management by James Brown, the author
discusses the importance of risk management, and having the correct risk management processes
in place can help provide project managers stability and structure whenever risks occur.
 References

LearningBridge Inc. (2003). Sample team charter - teamhelper.com. Team Helper.

https://www.teamhelper.com/sample/TC_GuideSample.pdf

Rose, K.H. (2014) Project Quality Management, Second Edition: Why, What and How (3rd Ed.)
Fl: J Ross Publishing. ISBN: 13: 9781604271935