Social Networking Team Operating Agreement

							Social Butterfiles




 Social Networking Team Operating Agreement




Project Name: Social Networking Applications
Project Manager Name: Katie Craggs
Project Sponsor: Professor Viscelli
Project Team Member Names: Michael Johnson; Adair Moore; Michael Creamer; Caitlin
Pittman
Date: March 20, 2009
Prepared by: All Team Members
PROJECT COMMUNICATION PLAN




Team Operating Agreement

Purpose of the Team Operating Agreement (TOA)
Our Team Operating Agreement serves as a specific outline to the duties and procedures needed
to successfully complete the project. It will sufficiently outline meeting times and goals for
deadlines to be met, as well as consequences for failing to meet with the group within scheduled
times and or deadlines. We hope that our TOA will ease the process in completing this project.


Mission Statement
To effectively work together as a team in order to successfully and coherently present Social
Networking Applications to our audience and receive the highest grade possible while doing so.
We will work together in order to present our researched topic through creating a website and a
live presentation with the use of a PowerPoint slide show.


Team Member Roles

Katie Craggs: Project Manager

       Schedule team meetings
       Facilitate effective communication within the group and the professor.
       Largely responsible for Team Operating Agreement
       Responsible for seeing that all assignments are completed and turned in on time.
       Participate in completing all other aspects of the project.

Formal Report Section:
             History of Social Networking Applications
Due Dates:
             Team Operating Agreement: March 20, 2009
             Web Page: April 2, 2009
             Formal Report: April 20, 2009

Caitlin Pittman: Presentation Coordinator.

       Be proficient with Microsoft PowerPoint
       Attain information from each member of the group.
       Integrate information into a well organized, informative presentation.

Formal Report Section:
            Introduction to Social Networking Applications

Due Dates:
                 Team Operating Agreement: March 20, 2009
                 Web Page: April 2, 2009
                 PowerPoint Presentation: April 16, 2009
                 Formal Report: April 20, 2009



SOCIAL NETWORKING APPLICATIONS                            PAGE 2                           3/20/09
PROJECT COMMUNICATION PLAN




Adair Moore: Formal Report Coordinator.

                Gather research from Research Coordinator.
                Make certain research is in correct format.
                Make sure everyone’s paragraphs flow well together as a whole.

Formal Report Section:
             History of Social Networking Applications

Due Dates:
                Team Operating Agreement: March 20, 2009
                Web Page: April 2, 2009
                Formal Report: April 20, 2009
                Completed Formal Report: April 21, 2009

Michael Johnson: Research Coordinator

      Coordinate academic articles.
      Incorporate resources.
      Check authenticity of the final project:
           o Make certain the appropriate attributions, citations, and references are placed
               correctly.

Formal Report Section:
             Technology needed

Due Dates:
                Team Operating Agreement: March 20, 2009
                Web Page: April 2, 2009
                Formal Report: April 20, 2009
                Completed Research: April 2, 2009

Michael Creamer: Web Site Coordinator
             Oversee final production of the web page.
             Make certain that all team members’ web sites look similar with proper
               formatting and styles.
             Make certain that they are all linked.
             Check for grammatical and spelling errors.

Formal Report Section:
             Current Issues with Social Networking Applications

Due Dates:
                Team Operating Agreement: March 20, 2009
                Web Page: April 2, 2009
                Formal Report: April 20, 2009
                Unified Web Page: April 2, 2009


SOCIAL NETWORKING APPLICATIONS                         PAGE 3                          3/20/09
PROJECT COMMUNICATION PLAN




Team Communications

                    All project information will be shared and saved on WebCT Vista and or an
                     external hard drive.
                    Team members will be reminded of meeting times and goals for the meeting at
                     least 24 hours in advanced through telephone or Vista e-mail.
                    Remember to be polite and open to all ideas and suggestions.
                    Communicate effectively within the group.
                    Remember to include everyone while creating and discussing new ideas or
                     concepts.
                    There are no stupid questions. Everyone needs to understand everything. If a
                     question arises, do not hesitate to ask.


Decision Making
   1. Decisions will be decided based on a majority vote. At least three group members are
      needed to win a vote.
   2. The team members will raise hands in order to vote.
             Hands up = agrees in favor of the decision.
             Hands down = disagrees with the decision
   3. All members must vote.
   4. Voting will only be necessary if verbal discussion cannot solve an issue in order to come
      to a conclusion.


Meetings

                     Team members will be prepared to state progress and what is left to be
                      competed
                     Team members will meet informally after classes on Tuesday’s and Thursday’s
                      in order to clear up any quick questions they have concerning the matter on
                      hand.
                     Formal meetings will be scheduled and followed according to the schedule
                      below.
                     Team members that suspect they will miss a previously scheduled meeting
                      should speak or meet with the team manager prior to the planned missed
                      meeting in order to give any material that may be needed during the meeting.
                     Failure to comply with above standard of missing meetings with result in the
                      following consequences:
           o       First missed meeting without notification: stern warning that group may follow
                   through with expelling the member form the group.
           o       Second miss meeting: group will meet to discuss the actions of group member
                   that has missed 2 meetings and decide if it is grounds for expulsion.
           o       If group vote cannot reach a majority, a third party (Viscelli) will be brought in to
                   vote on the matter as well.



SOCIAL NETWORKING APPLICATIONS                               PAGE 4                            3/20/09
PROJECT COMMUNICATION PLAN



                 Project manager will be responsible for reminding team of meeting times 24
                  hours in advanced.
                 Project manager will also be responsible for delegating meetings and keeping
                  them on track. She is also responsible for gathering and keeping track of all
                  completed material.
                 Remember to be punctual to all meetings. We will try to begin and end all
                  meetings on time. If meetings run over scheduled time, members will not be
                  responsible for staying late.
                 Team members are expected to show up themselves without the use of stand-
                  ins.
                 Each team member is responsible for keeping up with individual assignments
                  and material missed in the event that a meeting has been missed.




            March 19, 2009                             Discussing and creating TOA. Discussing
                                                       team members’ roles and responsibilities.
                                                       Discuss what will be needed for next
                                                       meeting.
            April 2, 2009                              Edit WebPages and make sure they are
                                                       uniform and correct. Discuss what will be
                                                       needed for next meeting.
            April 16. 2009                             Make sure final presentation is coherent
                                                       and correct. Practice reciting and
                                                       delivering final presentation. Decide if we
                                                       will need to meet again.
            Tentative April 19, 2009                   Continue practicing final presentation.
                                                       Begin discussing formal report if time
                                                       permits.
            April 21, 2009                             Edit and finish formal report to turn in.




Preparation and Quality
Each group member is expected to work to their highest potential and submit their best quality
work. A quality submission should be grammatically correct with no spelling errors as well as
thoroughly discussing their topic at hand. Team members also convey clear ideas to the audience
in regards to the formal presentation. Team members will be responsible to have his or her work
completed for review at the very least 24 hours in advanced. All work should be completed in time
for the group meetings. Only best versions should be submitted for review. Each member will
evaluate each other’s work through peer review and improve upon with opinions and suggestions.


Personal Courtesies

                 Each team member should work towards the success of the team as a whole.




SOCIAL NETWORKING APPLICATIONS                          PAGE 5                             3/20/09
PROJECT COMMUNICATION PLAN



               All communication devices should be silenced and not used as a distraction
                while group meetings are in session. Only in the event of an emergency should
                they be used.




Reviewed and approved by:


________________________________________________              ____________________
Project Manager                                               Date:
________________________________________________              ____________________
Project Team Member Name                                      Date:
________________________________________________              ____________________
Project Team Member Name                                      Date:
________________________________________________              ____________________
Project Team Member Name                                      Date:
________________________________________________              ____________________
Project Team Member Name                                      Date:




SOCIAL NETWORKING APPLICATIONS                       PAGE 6                          3/20/09