Team B6
Team Operating Agreement
Project Name: Pending
Project Team Member Names: Mackenzie Drummond, Guoge Cheng, Samihan Shani
Date: October 12th, 2016
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.
Team Communications
The team will communicate via canvas. We have a group text but only to direct the group to canvas when someone isn’t responding via canvas. All project documents will be stored on google drive and will be shared with the group. We are still working on specific days we all can meet, but if our schedules do not work we always have class and can do skype conferences. If there is ever a problem we all agree to be upfront and honest about how we feel. Once we determine what our project will be we will outline the course of action and tasks will be distributed. This will be more clear once we pick our project.
Team members will appreciate the sensitive nature of information discussed during this project and will share with care. Where applicable, documents will include a footer indicating that information is confidential.
“Sidebar” conversations between team members during team meetings will not be allowed. All communication will be open and courteous. No “over talking” or interrupting.
Team members will keep each other informed at all times.
Decision Making
- Consensus means that everyone can live with the decision. It doesn’t mean everyone has to agree 100%.
- The team will use thumbs up/thumbs down voting to make decisions quickly and move on. Anyone on the team may call for a vote at any time.
- Thumbs up = agree with no further discussion.
- Thumbs sideways = agree, but have further questions. (Questions will be asked and answered immediately after the vote.)
- Thumbs down = cannot agree to the solution proposed. (Be prepared to answer the question: What would it take for you to go to thumbs sideways or thumbs up?)
- No decision is made if there are any thumbs-down votes.
- Members may abstain from voting.
- Some complex decisions will be taken after in depth discussion of the problem.
Meetings
- Project team members will report status at each team meeting.
- Project team members will meet [to be determined once we establish project]. During each meeting, a “parking lot” will be used to record topics that require discussion at a later date.
- Issues, risks, change requests, and action items will be reviewed and updated at each meeting.
- The project facilitator 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.
- The project facilitator outlines meeting beforehand- important points to go over and discuss.
- The project note taker records during meeting and posts summary to google drive so we can look back at what was said and agreed on
Facilitator and note taker change each week
- 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.
Personal Courtesies
- 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 project.
- All cell phones and other communication devices must be silenced during meetings and used on an exception basis only.
Reviewed and approved by:
Mackenzie Drummond Date: 10/12/16
Guoge Cheng Date:10/12/16
Samihan Shani Date: 10/12/16
