Team Charter

Mark Jayson Escalona: 300373102

Dishan Pathiraja: 300362943
Josue Garcia:300371940
Raghav Kapoor: 300364996
Amanpreet Kaur: 300346292
Parker Hughes: 300321535

BUSN 3620: Managing Project Time and Scope

Professor Min Jin Kim

1
 Table of contents

Team Charter ................................................................................................................................................ 3

1.0 Members --------------------------------------------------------------------------------------------------- 3

2.0 Primary Goals and Objectives -------------------------------------------------------------------------- 3

3.0 Roles and Responsibilities -------------------------------------------------------------------------------4

3.1 Rules of Behavior -----------------------------------------------------------------------------------------4

4.0 Team Meetings --------------------------------------------------------------------------------------------6

5.0 Information Sharing --------------------------------------------------------------------------------------6

6.0 Decision Making ------------------------------------------------------------------------------------------6

7.0 Managing Conflict ---------------------------------------------------------------------------------------7

8.0 Penalties ---------------------------------------------------------------------------------------------------7

2
 Team Charter
Project Group Name: Catalysts
Date: 31st May 2023
Document Number: 001

Approvals:
Created
Designation Date of Issue Revision
by
MJE / PLH Project Manager/ 31st May 2023 0
Data & Risk

Section for revision:

Revision Name of
Description Created by
Date approver

List of Distribution:

Revisio
Name Designation Date of Issue
n
Mark Jayson Escalona Project Manager 31/05/2023 0
Project Coordinator,
Dilshan Pathiraja 31/05/2023 0
Scrum Master
Project Communicator
Josue Garcia 31/05/2023 0
& Conflict Resolver
Raghav Kapoor Agile & PERT Expert 31/05/2023 0
Amanpreet Kaur Editor 31/05/2023 0
Parker Hughes Data & Risk Analyst 31/05/2023 0

3
1.0 Members:

Member Name Email Contact

Number
Mark Escalona escalonam2@student.douglascollege.ca +1(780)0389976
Dilshan Pathiraja ganeearachchipr@student.douglascollege.ca +1(604)6521992
Josue Garcia garciatalaveraj@student.douglascollege.ca +1(236)8689594
Raghav Kapoor kapoorr2@student.douglascollege.ca +1(778)8731621

Amanpreet Kaur a5@student.douglascollege.ca +1(236)5167691

Parker Hughes hughesp3@student.douglascollege.ca +1(604)3098375

2.0 Our Team’s Primary Goals & Objectives:

2.1 Goal 1: Achieve a successful project

Objectives:
 Understand project needs and expectations thoroughly.
 Maintain open communication channels to ensure ongoing assessor
feedback and satisfaction.

2.2 Goal 2: Deliver Final Project on time

Objectives:
 Develop a clear understanding of project requirements
 To meet and anticipate the project deliverables deadlines.

2.3 Goal 3: Boost Effective Communication and Collaboration

Objectives:
 Establish open and transparent communication channels within the
team.
 Encourage active listening and constructive feedback among the team
 Establish a platform for sharing and discussing ideas to enhance
collaboration

4
3.0 Roles and Responsibilities:

Member Team Role Assigned Tasks

Name
Mark Jayson Project Manager  Define the project requirement.
 Manage and monitor all the tasks.
 Facilitate meetings.
 Do follow ups on assigned tasks and
deadlines with team.

Dilshan Project  Submit the document to the instructor on

Pathiraja Coordinator,
the blackboard on time.
Scrum Master
 Assist PowerPoint presentation document.
 Help the team to stay on track with the
assigned activities.

Josue Garcia Project  Communicating with the all-team members

Communicator &
and the professor for additional information.
Conflict Resolver
 Help to resolve the issues in the team.
 Do proof reading.

Amanpreet Agile & PERT  Delegate Tasks

Kaur Expert
 Checking the spelling and grammar.

Raghav Editor- Graphics,  Standardize the format and layout of the

Document
Kapoor document.
Formatting
 Final editing to team’s document and Power
Point presentation.

Parker Project  Define product requirement.

Coordinator
Hughes  Define changes in product requirement.
 Updates backlog.

3.1 Rules of behavior:

 Every team member is to contribute to the deliverables equally (to the

extent possible).
 Every team member will be treated with respect. Harassment and
bullying will not be tolerated.

5
  All members will work in a safe environment free of discrimination
(racism, sexism, etc.)
 No team members shall plagiarize.
 Team members are to respect each other's individual time requirements
(not everyone has the same work/class schedule).
 Attendance is mandatory for all lectures and meetings (to be tracked
with a meeting/action log).
 If a member is unable to attend a meeting, he/she must notify the group
so that appropriate arrangements are made.
 All decisions will be made as a group based on majority vote.

4.0 Team meetings:

Weekly
 Online: Thursdays, or Friday, or Saturday or Sundays
Frequency
10:00 pm
 In-person: Wednesdays 9:30 pm, after class
Remote or In Person (at Douglas College, New Westminster).
Location The location depends on the work and other commitments of
all the team members. Via Zoom or Microsoft Teams.
Purpose Brainstorming, Review each other’s work, Monitor progress.
All members should attend remotes or in person to all these
Rules
meetings, encourage participation and sharing of activities.

5.0 Information Sharing:

 OneDrive for shared documentation

 Zoom or Google meet for virtual meetings and screen sharing
 WhatsApp and College email for collaborative communication and
instant messaging

6.0 Decision Making :

Decisions in the project will be made through team discussions and active
participation. We will share information, evaluate options, and aim to reach
a consensus. Once a decision is made, it will be documented, responsibility
will be assigned, and communication will be ensured. We will consider
diverse perspectives and strive for informed decisions that align with the
project's objectives.

6
7.0 Managing Conflict :

Conflict Solution
Communication issues Bring into highlight the code of ethics and the standard
group norms, where communication is important.
Therefore, any communication gaps will be handled with
the entire team’s involvement. An irresponsible team
member will be dealt with formal warnings and penalties.
Not meeting deadlines Everyone is equally responsible for meeting deadlines with
their assigned tasks. If any member is having any personal
issues, they should be communicated to the group who
comes in advance, so that others have time to manage.
Issues in content Peer work will be reviewed and ask for making any changes
quality needed to the content or formatting, with the support of
any member who understands and is willing to devote time
for the assistance.
Not being supportive Non supportive members will be reminded that this is group
work with unified goals/s and that everybody’s commitment
leads to build synergies to make the group work a success.
Extreme cases will be dealt with penalties.

8.0 Penalties :

1. First Warning: If someone does not follow the project charter, they will
get a formal text or email explaining the problem. They will have 12
hours to respond and fix the issue.
2. Second Warning: If the person keeps ignoring the project charter and
does not respond to warnings, they will have to buy coffee for the
whole team during the next meeting. This is to show them the
importance of their responsibilities.
3. Third Warning: If the person still does not improve after the first two
warnings, a formal message will be sent to them, copying all the team
members and the module instructor. The team leader will be
responsible for sending this message. This is a serious step to involve
higher authorities and resolve the issue.
4. Team Discussion: If the person continues to ignore the project charter,
the team will have a meeting to talk about the problem. Everyone will
share their concerns and try to find a solution together.
5. Revised Responsibilities: As a consequence of not following the project
charter, the person may be assigned different responsibilities or tasks.
This is done to minimize the negative impact on the project and allow
other team members to work better.

7
6. Formal Escalation: If the non-compliance persists and affects the
project and team dynamics, the team leader or project manager will
inform the course instructor or project supervisor. They will provide a
detailed report with all the previous warnings and actions taken to
address the situation.
7. Consequences: The course instructor or project supervisor will decide
the appropriate consequences based on the severity of the non-
compliance. This can include grade deductions, reassignment, or other
disciplinary actions as needed.