Download Purpose of the Team Operating Agreement

The CPSN Group
Consulting Co. Team Operating Agreement
Project Name: Consulting Co.
Project Manager Name: Christian Nelms
WebMaster: Nicholas D Ellis
Formal Report Coordinator: Shaye Whiten
Research Coordinator: Pamela May
Presentation Coordinator: Sarah Clemens
Date: 15 October 2013
Prepared by: Nicholas D Ellis
PROJECT COMMUNICATION PLAN
Team Operating Agreement
Purpose of the Team Operating Agreement (TOA)
This TOA serves as the guidelines and ground rules to help the project team work most
productively together over the course of the project. The TOA is a living document and may be
updated as the need arises throughout the project. Any updates will be discussed with and
ratified by the project team members.
Mission Statement
The CPSN Group is committed to maintaining customer satisfaction, trust and integrity by
delivering quality products and services conforming to industry best practices and
continuous process improvement.
Objective
The objective of this group is to become informed, through research, about data mining and data
warehousing, in order to present the information in an appealing way to our fellow classmates. As
a group, we will accomplish this large task by breaking the project down into roles, which group
members will take on and complete independently. At the end of the project, the group will come
together and collaborate, using all of the information found during the project, to create an easily
understandable, appealing presentation.
The research topic that this group has been assigned is data mining and data warehousing. In
our presentation, we will include the following:
• Introduction to Data Warehousing/Data Mining. This is a research- intensive section and
should reveal the main concepts behind data warehouses and data mining techniques
from a technical perspective.
• Discussion of Business uses of Data Warehousing/Data Mining. This section should
include specific uses for the technologies in a business setting.
• Discussion of particular tools available in the marketplace and their intended business
use (for example, are some tools intended only for large enterprises, and some for
smaller businesses).
• Discussion of the costs (where available), resource needs, and other considerations for
organizations considering these technologies.
• Summary of Report findings
When we present our research, we will use a video, a power point presentation, and a formal
report to introduce the class to data mining and data warehousing. For our presentation, will need
to rent a video camera from the library, rent a workspace, where we can record our presentation
video, and a jump drive to put our presentation on. For our formal report, we will need a binder,
dividers, paper, and a folder.
THE CPSN GROUP CONFIDENTIAL
PAGE 2
OCTOBER 18, 2013
PROJECT COMMUNICATION PLAN
Preparation and Quality




Each team member represents a specific area of expertise or business unit. Team
members will bring their individual perspectives to the team and will also consider
what is best for the company.
All members are required to do quality work. Quality is defined by the best possible
work completed and reviewed by all peers. All work matches up to the rubric in order
to reach the best possible grade.
Work must be submitted by internal dates for peer review and adjustments.
PM will keep up to date progress of active deliverables.
Decision Making
1. Consensus means that everyone can live with the decision. It doesn’t mean everyone
has to agree 100%.
2. The team will utilize specialty decision making. The individual help responsible for the
task will have majority decision making.
3. Project Manager will be final decision maker if there are any discrepancies made.
4. Meeting minutes will document the decisions made. If you have questions after reviewing
the minutes, contact the project manager and determine the course of action, such as to
bring questions to the team for discussion again.
Work Breakdown Structure
External Dates and Deliverables






Team Operating Agreement - Friday 10/18 at 5pm – Nicholas Ellis
Team Website - Friday 10/25/13 at 5pm – Nicholas Ellis
Team Progress Report - Friday 11/8/13 at 5pm – Christian Nelms
Team Formal Report - Wednesday 11/20/13 due in class @ 5pm – Shaye Whiten &
Pamela May
Team Presentation - Wednesday 12/4/2014 due in class @ 5pm - Sarah Clemens
Team Member Evaluation - Due in class Wednesday 12/4/2013 will close on
12/5/2013 – Individually completed
Internal Dates and Deliverables






Team Operating Agreement - Friday 10/18 at 5pm – Nicholas Ellis
Team Website - Friday 10/23/13 at 5pm – Nicholas Ellis
Team Progress Report - Friday 11/6/13 at 5pm – Christian Nelms
Team Formal Report - Wednesday 11/18/13 due in class @ 5pm – Shaye Whiten &
Pamela May
Team Presentation - Wednesday 11/28/2014 due in class @ 5pm - Sarah Clemens
Team Member Evaluation - Due in class Wednesday 12/4/2013 will close on
12/5/2013 – Individually completed
THE CPSN GROUP CONFIDENTIAL
PAGE 3
OCTOBER 18, 2013
PROJECT COMMUNICATION PLAN
Team Meetings and Attendance Policy











Project WebMaster leaders will report status at each team meeting.
Project team members will meet Mondays, 8:00PM, 1st floor Burrus Building. If
necessary Tuesdays, 4:00PM. Necessary is 75% group members vote yes to
meeting.
Meetings will last 30-45 minutes, unless deemed necessary to shorten or lengthen
meeting time.
Issues, risks, change requests, and action items will be reviewed and updated at
each meeting.
The project manager will be responsible for facilitating and keeping meetings on
track. Team members will accept the project manager’s decision to table or “park” a
discussion topic.
Meetings will start and end on time. Team members will attend meetings in person
when feasible. A dial-in number will be available for remote attendance.
Sending “stand ins” to meetings will not be allowed unless approved by the project
manager prior to meetings.
It is the responsibility of each team member to stay current on the project team
activities, even when he or she has missed a meeting.
Missing a meeting without notice will be allowed only twice before the Project
Manager contacts Professor Perry and seeks dismissal from team.
4 absences may be allowed if notice is given 3 hours prior as well as a sufficient
excuse. (75% of members in attendance agree it is a legitimate excuse.)
All cell phones and other communication devices must be silenced during meetings
and used on a limited basis only.
Non-Performance



Poor performance will be evaluated on a case by case bases. Root cause will be
evaluated and determined by the PM what could have been improved. If no help was
requested or the poor performer clearly chose not to perform well, PM has option to
escalate issue to Professor Perry.
All members are held responsible to internal deadlines as well as external deadlines.
Each member will be held 80% responsible for deliverables assigned to their role with
the support from their peers holding the other 20%.
Team Communications




The project’s Google Docs will house the most up-to-date version of project
documents. All team members will be given access.
Meeting agendas will be e-mailed to project team members at least 24 hours prior to
meetings. Meeting minutes will be posted to the project Google Docs site within 24
hours after meetings.
Meetings will occur regularly on Mondays at 8:00pm for a maximum duration of 45
minutes. When agreed upon by 75% of the group, meetings will be held Tuesdays at
4:00pm for same maximum time period.
Team members will appreciate the sensitive nature of information discussed during
this project and will share with care.
THE CPSN GROUP CONFIDENTIAL
PAGE 4
OCTOBER 18, 2013
PROJECT COMMUNICATION PLAN





“Sidebar” conversations between team members during team meetings will not be
allowed.
All communication will be open and courteous. No “overtalking” or interrupting.
Team members will keep each other informed.
Communication will be via Phone call, Text, Email, and D2L. Members must use 2
mediums to guarantee message was received.
Members must respond within a 12 hour time period.
Description of Roles
Formal Report Coordinator (RC):
The Formal Report requires input from all team members. Each member must sign off on the
report prior to submission.
The Formal Report Coordinator is the structural leader of the report. This individual will take the
research provided from the Research Coordinator and create an outline of the formal report. Each
team member is responsible for writing an equal portion of the formal report and will receive an
individual grade for their effort. The FRC will integrate portions of the written report from each
team member and will communicate frequently with the PM and RC for additional references.
This individual should possess strong time management, business writing, MS Word skills, and
will be spending some time in the writing lab. Every team member must submit a copy of the
finished formal report through their WebCT assignment icon, so time for review and team
feedback must be built into the schedule. The RC will focus on Title Page, Prefatory Parts,
Supplemental Parts, Headings, TOC, and all required elements of the sample report in Chapter 9.
Research Coordinator (RC):
The Researchers job requires early project participation. This individual will be one of the first
team members to execute their roles.
The Lead Researcher is a critical evaluator of resources used in the final project. This individual
should be well versed in Internet and library database searches. They will be responsible for
coordinating academic articles, white papers, and corporate resources.
Each team member is responsible for providing resources to the project, and will receive an
individual grade for their effort; but will do so with the assistance of the research coordinator. The
RC will also be responsible for checking the authenticity of the final report, including appropriate
attributions, citations, and references. This individual should possess attention to detail and will
be spending some time in the library.
Knowledge of APA style a plus.
Presentation Coordinator (PC) also known as the Digital Video Coordinator:
The Presentation is an integrated project in which all team members must participate.
Everyone must assume attend presentation rehearsals and accept equal time in a presentation
role
The Presentation Technologist is the technical lead on the digital video (if DV is used) and the
presentation organizer. The individual will choose an organizational pattern for the presentation,
will assign roles to team members based on their areas of expertise (corresponds with section of
the report written), will structure the introduction and conclusion, and set rehearsal times.
THE CPSN GROUP CONFIDENTIAL
PAGE 5
OCTOBER 18, 2013
PROJECT COMMUNICATION PLAN
Presentation slides ARE NOT used during in class presentations. For video classes, this
individual will choose a setting for the presentation
– schedule camera checkout, coordinate production schedules with team members, shoot the
video footage, and edit the digital video file. The PC is responsible for submission and publication
via WebCT VISTA. No previous experience with digital video is needed.
KSU campus supports iMovie. Each team member is responsible for writing, rehearsing, and
speaking a part of the final presentation, and will receive an individual grade for their effort. This
individual should good leadership abilities and if using DV, will be spending some time in the
Presentation Technology Department.
Project Manager (PM):
The Project Manager will be the primary team communicator and coordinator. This individual will
participate in each of the three team deliverables (Web page, report, and presentation) while
simultaneously coordinating meeting times, communication, and assignment submission
procedures.
This individual will coordinate all activities of the team. They will take the lead role in completing
the team Operating Agreement and will be an active participant with the
Formal Report Coordinator, Web Page Coordinator, and Presentation Coordinator.
This individual should have strong communication and planning skills. They will construct a
timetable for the project, manage all team communications, and submit the formal report to
turnitin.com with time for revisions if necessary. The PM will take ultimate responsibility for the
timely completion of each related project. This includes monitoring of the discussion board,
reminder emails to team members, and participation in projects as needed by other members.
Web Site Coordinator – Web Master (WM):
The webpage is an integrated project, combining pages from all team members into one final web
page layout, with navigational capabilities to each team member’s page.
The Web Master will coordinate with team members on page layout, design, and style. A
common theme will be chosen that must be used on each team members page. The Web
Master will work with team members to create, edit, link, and upload the final page.
Each team member is responsible for creating their own page, and will receive an individual
grade for their effort; but will do so with the supervision and support of the Web Master. This
individual choosing to accept the role of Web Master should be acutely aware of the Web Page
assignment requirements. No previous web design experience is required. This individual should
possess attention to detail and will be spending some time in the computer lab. Knowledge of
Web composing software or HTML a plus. All students will post the ENTIRE website. It is like
having 5 identical houses with 5 individual addresses.
THE CPSN GROUP CONFIDENTIAL
PAGE 6
OCTOBER 18, 2013
PROJECT COMMUNICATION PLAN
Reviewed and approved by:
Christian Nelms
________________________________________________
Project Manager
10/18/13
Date:
____________________
10/18/13
Nicholas Ellis
Date:
____________________
Shaye Whitten
Date:
____________________
Pamela May
Date:
____________________
Sarah Clemens
Date:
____________________
________________________________________________
WebMaster
________________________________________________
Formal Report Coordinator
________________________________________________
Research Coordinator
________________________________________________
Presentation Coordinator
THE CPSN GROUP CONFIDENTIAL
PAGE 7
10/18/13
10/18/13
10/18/13
OCTOBER 18, 2013