Honeypot Project

Fall '05

Operating Agreement

*Team Pender*

Mission Statement

“To bring out the best in each other in pursuit of excellence.”

I. Preliminary Provisions

(1) Effective Date: This operating agreement binds all team members effective November 1st 2005. By signing this agreement, each team member agrees to abide by the terms set forth in this document.

(2) Formation: The team is comprised of five similar-minded students of BISM 2100 operating under consistent goals and objectives.

(3) Name: The members of this team operate under the formal name of Team Pender

(4) Purpose: The purpose of this team is to produce a Formal Report, Team Web Page, Video Presentation, etc in correlation with the end-of-semester project set by Professor Elke Leeds for BISM 2100, Section 04.

(5) Goals: As a team, we will strive to meet all deadlines, attend all required meetings, communicate clearly with one another, and give our very best in pursuit of excellence. We will learn from one another, support one another, and hold each other accountable in the assigned tasks.

(6) Roles:

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.

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.

Digital Video Presentation Coordinator (PC):

The Digital Video 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. 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 the final submission via the WebCT TEAM HOMEPAGE. An understanding of hyperlinks and uploads is a must. No previous experience with digital video is needed. KSU campus supports iMovie. Other DV editing programs are acceptable, but campus and instructional support will not be provided. 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. No previous DV experience is necessary. This individual should good leadership abilities and will be spending some time in the Presentation Technology Department. Having your own mini-DV a plus.

Forma l Report Coordinator (RC):

The Formal Report requires input from all team members. Each member must signoff on the report prior to submission.

The Formal Report Coordinator is the lead writer. 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 a 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.

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 Digital Video 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 turn in 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.

(7) Schedule of Deliverables:

· November 18, 2005: Formal Report

· November 25, 2005: Web Page

· December 2, 2005: System Presentation

· December 6, 2005: Individual Assignment Presentation Review and Analysis.

II. Membership Guidelines

(1) Communication: Each member will communicate as clearly as possible. In order to maintain transparency to the entire group, the majority of communication should be conducted through the WebCT team forum. When requesting assistance from other team members, a member will communicate what he or she needs and an initial deadline for a response. If the assisting team member believes the deadline to be unreasonable, it is the responsibility of the assisting team member to provide an alternate deadline.

(2) Meetings: The team shall meet for 15-20 minutes after each class for progress reports on all assignments.

(3) Management: Team members are expected to manage their time efficiently for each project. If a team member believes he or she cannot meet an existing deadline, it is that member’s responsibility to communicate this challenge to the group along with an alternate resolution.

(4) Decision Making: All issues brought to the table concerning the team and assignments will be considered and discussed. Decisions will be made by a majority vote.

(5) Deadlines: Team members will meet all deadlines set by the team. If a member cannot meet a deadline, he or she will contact the other members; provide a reasonable explanation and a resolution to the problem. In the case that a member does not complete an assignment by the deadline, he or she will be subject to the terms set forth under the disciplinary section of this agreement.

(6) Membership Withdrawal: A team member may not voluntarily withdraw from the team unless under very serious circumstances which prevents him or her from completing the school semester.

(7) Disciplinary Measures: The team shall not tolerate the following behaviors and will regard such conduct as OFFENSES:

a. Missing meetings without notice.

b. Failure to participate in and contribute towards all team assignments.

c. Failure to submit one’s project assignment on time.

d. Negative and disrespectful remarks to other team mates.

Should it become necessary to discipline a member of the team, the offending member will be penalized as follows:

a. For the first offense, the member will forfeit 10% of his or her grade for the individual assignment. At her discretion, Professor Leeds may award this 10% adjustment to the offended team member(s).

b. For the second offense, the member will forfeit 20% of his or her grade for the individual assignment. At her discretion, Professor Leeds may award this 20% adjustment to the offended team member(s).

c. On the third offense, the member will receive a failing grade on the assignment and will be removed from the team.

III. PROJECT REQUIREMENTS AND SCHEDULE:

(1) Project Breakdown:

a. Formal Report: Each team member will be assigned a part of the written formal report. The Formal Report Coordinator will see to it that all parts of the assignment are put together in a clear, concise and complete manner. The final Formal Report will be subject to approval of all team members.

b. Research: Each member must provide a minimum of three research resources (e.g. websites, reports, books) for their part of the Formal Report. The Research Coordinator shall coordinate all research and provide the Reference List portion of the Formal Report.

c. Web Site: Each team member will be held responsible for their individual web page. The Web Site Coordinator shall coordinate all pages on the team website. The final team Web Site will be subject to approval of all team members.

d. Digital Video Presentation: All team members will be responsible for a part of the final presentation. The DVP Coordinator shall perform his or her team role as listed in the Member Team Roles section of this Operating Agreement.

(2) Project Schedule:

-Operating Agreement:

a. Rough Draft of opinions due November 7

b. Final Provision on Tuesday, Wednesday November 8, 9

c. Due Thursday November 10

-System Analysis Paper and Peer Evaluation:

a. Rough Drafts of each members part, due Thursday November 10.

(Review paper for main points for Presentation)

b. First Provision Due Monday November 13 and sent out to all members

for opinions.

c. Final product due Tuesday November 15 (If all members agree to

Satisfactory, paper can be turned in)

d. Paper due Friday November 18 to Prof. Leeds.

-Webpage:

a. First Draft of webpage due Friday November 18

b. First provision of webpage to be completed by Monday November 21

c. Final product Wednesday November 23 (Turn in if agreed upon, via

email)

d. Webpage due Friday November 25 to Prof. Leeds (Remain in

contact through the holiday via email/cell phone)

-System Presentation:

a. Rough draft of each member’s part of what he/she is talking about; due

November 25 (via email)

b. First provision due for each member to critique each other, due

November 28 (via email/or meeting; mock presentation)

c. Final practice session December 1 (mock presentation, and last minute

touches)

d. Due December 2 to Prof. Leeds.

-Individual Assignment Presentation Review and Analysis:

a. Rough Draft of assignment due Wednesday November 30

b. First provision of work due by Friday December 2

c. Final review and analysis finished and due Sunday December 4 (via

email)

d. Due December 6 to Prof. Leeds

IV. MEMBER SIGNATURES:

(1) Execution of Agreement: In witness whereof, the members of this team will agree and adhere to this agreement set forth on (Date), as operating agreement of this team.

Signature:_______________________________ Member