Team 5 Operating Agreement

Reviews
Shared by: johnrr2
Stats
views:
13
rating:
not rated
reviews:
0
posted:
12/10/2008
language:
pages:
0
Team 5 Operating Agreement Team Members:       Keiandra Fuller – Research Coordinator Sean Goudelock – Web Site Coordinator Joel Goyne – Project Manager Amber Hamby – Research Coordinator Tanner Hart – Presentation Coordinator Terry Hoeye – Formal Report Coordinator Table of Contents TEAM OBJECTIVE AND MISSION STATEMENT........................................................................2 DECISION-MAKING ...............................................................................................................................3 MEETING ATTENDANCE POLICY AND SCHEDULE ................................................................4 PREPARATION AND QUALITY..........................................................................................................4 NON-PERFORMANCE AND PEER-REVIEW ................................................................................5 WORK BREAKDOWN STRUCTURE ................................................................................................5 SIGNATURES OF AGREEMENT ........................................................................................................6 Team Objective and Mission Statement Our team objective is to complete the project in a timely manner, while accomplishing the best grade possible, most preferably an A. We will accomplish our goal by consistently having all of the team members at our meetings, and completing all of the assignments well before they are due. Checking WebCT frequently is a must, as that will be where all of the information is passed along to each of the team members. The purpose of the assignment is to effectively inform our audience about podcasting in a business setting through the following:  This project will use all of the skills that we have obtained throughout the semester, and help us to learn how to combine all of these skills and apply them in a business setting. The grade our team obtains through this project will heavily impact each team members final grade in the class This project will show how our team can take a formerly unknown topic, and make it something that each member will be able to discuss knowledgably if it ever comes about in a casual conversation or in the workplace We can use the information we have learned through this project as podcasting continues to emerge as a tool in the business world, and use it to our advantage, putting us ahead of those who do not have knowledge of the technology. We know that for this project we will need o 20 references to receive full credit o 10 commercial and 10 academic resources o To incorporate charts, graphs, and other visual aids to illustrate our points o To turn it in to www.turnitin.com in an effort to prevent plagiarism o To realize that we will not be able to take excerpts from our resources without proper referencing of where the information was obtained from o To film our presentation and submit it into WebCT o The Webmaster to make sure that each of the webpages flow together with a similar theme.     o To recommend ways that podcasting can be used in the classroom, the workplace, and in our everyday lives We will need to research the following information about podcasting        The Basics of Podcasting The History of Podcasting Podcasting Technology Current Issues of Podcasting Podcasting in Business Podcasting in Education Detailed Recommendations on Incorporating Podcasting in Higher Education We will present our findings in a written report, having a printed copy and an electronic copy on hand, as well as a video of our presentation We will need the following to complete our project:   A computer to type our project on A video camera to film our presentation on Decision-Making All decisions will be made using a democratic process of voting, where the majority wins, but those issues of the minority will be taken into account, and be discussed in case that they present a good idea that will benefit the project. Since there are six group members, there will always be a possibility of a tie. If this occurs, we will go around the table asking the opinion of each member. After everyone has a chance to debate and discuss the matter, the group will revote. If there is another tie, the Project Manager’s vote will count twice. Meeting Attendance Policy and Schedule Meeting Policy: We will meet every Tuesday at 5:00 pm on the third floor of the library, with Thursdays being used as a time where we can meet if needed. Four meetings will be needed to be attended, if less that four meetings are not attended, a penalty of five points will be assessed per meeting not attended if the goal of four meetings were not met unless extreme conditions arise. March 25, 2008 –Preparing our team’s Operating Agreement for submission on Sunday, March 30, 2008 by 11:59 pm April 1, 2008 – Begin working on the webpages as a team April 8, 2008 – Finish our team webpages so that they are ready for submission on April 13, 2008 April 15, 2008 – Begin working on the formal report April 22, 2008 – Finish formal report for submission on Sunday, April 27, 2008 by 11:59 pm. Preparation and Quality As a team, we believe that each submission should be properly formatted, free of spelling and grammatical errors, and be coherent. All information should be given to the project manager on the Thursday before each part of the project due for submission. Only the best versions will be submitted for review. Once each part of the project is completed, it will be posted on WebCT so that the group can easily access the document, and make recommendations before the final due date. Non-Performance and Peer-Review Each member of the team has two responsibilities: Show up to four out of the five meetings, and have each part of their project turned in on the Thursday before it’s due. If a team member does not perform up to the standards of the team, the team will meet with that person and discuss what penalty will be assessed. The team members that put the most into this project will evenly split ten bonus points as a reward for their hard work. Work Breakdown Structure Thursday, March 27th, 2008: Operating Agreement due to the project manager by 11:59pm. Thursday, April 3rd, 2008: The website should be started, and over halfway complete for the Web Site Coordinator to review by 11:59pm. Thursday, April 10th, 2008: Web pages should be complete and be able be reviewed by the Web Site Coordinator by 11:59pm. Thursday, April 17th, 2008: All of the resources being used in the final report should be sent to the Research Coordinator by 11:59pm. Formal report should be started and progress should be sent to the Formal Report Coordinator by 11:59pm. Thursday, April 24th, 2008: Formal report should be completed and sent to the formal project Coordinator by 11:59pm. History of Podcasting – Terry Hoeye Podcasting Technology – Sean Goudelock Podcasting in Business – Tanner Hart, Keiandra Fuller Podcasting in Education – Joel Goyne Current Issues in Podcasting – Amber Hamby Signatures of Agreement Keiandra Fuller Keiandra Fuller Sean Goudelock Sean Goudelock Joel Goyne Joel Goyne Amber Hamby Amber Hamby Tanner Hart Tanner Hart Terry Hoeye Terry Hoeye

Related docs
Team_Operating_Agreement
Views: 135  |  Downloads: 6
joint operating agreement task force
Views: 7  |  Downloads: 0
TEAM HEALTH INC Employment Agreement
Views: 5  |  Downloads: 0
Team Agreement
Views: 16  |  Downloads: 0
Team Development
Views: 1270  |  Downloads: 198
Booklet 5 5 FRANCHISING
Views: 1  |  Downloads: 0
Operating Agreement Example
Views: 28  |  Downloads: 1
Team-Rosters
Views: 5  |  Downloads: 0
improvement team
Views: 7  |  Downloads: 1
Operating Agreement Example
Views: 847  |  Downloads: 78
pllc operating agreement
Views: 96  |  Downloads: 3
team building-Team Building Mentoring.pdf
Views: 0  |  Downloads: 0
Other docs by johnrr2