TEAM Rulescsc 190 Spring 2017

TEAM RULESCSc 190 Spring 2017

IOHWIS

The Team Agreement is compiled and agreed upon by the group of 6 (six) senior students, working together as a team on development and completion of the chosen and approved Senior Project. The Team Agreement should develop the sense of shared responsibility, increase member`s awareness of personal behavior, enhance the quality of the group work. The Team Agreement is to be reviewed and updated if necessary in the beginning of each Sprint.

Meetings rules:

• Be on time for the meetings
• If late or not able to participate in a meeting (including Tuesday lectures), inform ahead of time
• Leaving the meeting on time
• Have clear agenda in mind and on paper (if necessary) before and after the meeting
• If needed, prepare questions ahead of time
• If half of the team or less is going to be absent, reschedule for different time
• Client meetings require at least half of the team present

Communication/Contribution rules:

• Use the group text messaging as a means of communication between the meetings
• Use personal or team`s email for larger texts or any attachments
• Respect your teammates
• Don`t be afraid to voice your opinion or ideas.
• Everyone has equal voice and valuable contribution. Everyone`s opinion is important!
• Make decisions together
• If changes to the work (process, code, documents) are made, inform others about them
• It is OK to disagree with each other, but no personal attacks
• Discuss the merit of ideas, not the people
• Be transparent: give, receive, and act on feedback
• Be responsible for the work assigned and accountable to your commitment
• Solve roadblocks together, don`t be afraid to ask for help
• If the problem can`t be solved by the team, as a team ask superior such as SCRUM Master
• The whole team has responsibility to question when someone is breaking the agreement
• Revisit the agreement from time to time and update the rules if needed

Definition of “DONE”:(to be discussed by the team)

• Check here:

TEAM INTEGRAL AGREEMENT

This is an official agreement of behavior among and expectations of team Integral. By signing you

agree to all terms listed below.

1) Team Meeting:

a) Weekly team meeting time Fridays at 5:30pm

b) Come to seminar (Class meeting) every week

c) Notify group in slack if you are unable to attend seminar or the weekly meeting;provide reasons

d) Faculty Advisor meetings once a week by team (time/date TBD)

e) Client meetings are mandatory

2) Teamwork:

a) Utilizing Github to store and work on all relevant materials related to the project

b) Team members check Slack regularly, at least daily, and respond asap toquestions and comments ASAP

c) Work in at least pairs (no one works alone)

i) Pairs are still part of the team (not an isolated group)

ii) Pairs divide work equally (members of subgroups should share theworkload as much as possible)

3) Expectations:

a) Be honest and to the point

b) Respect each other, the client, and their goals and projects

c) Act with integrity and with the team’s best interest in mind

d) Communication is key

e) Have a willingness to learn and try new techniques

f) Share your experience when necessary to the benefit of the team

4) Problem Solving:

a) Maximize your time for efficient usage

i) Ask the team if you run into a difficult problem you can't quite solve

5) Trust:

a) Do not plagiarize someone else's code and pass it off as our/your own

b) Members of the team should put full faith and effort towards the success of theteam; likewise the team shall put its full faith behind it's team members

c) If outside sources are used, then reference them appropriately and give them duecredit

6) Violations :

Violations of this agreement are defined as the following:

a) Inability to provide notice of absence OR a reasonable excuse within one weekprior to OR after a mandatory, scheduled event

b) Discrimination or harassment of a physical/verbal nature

c) Demonstrated unwillingness to participate in team activities, planning events orcoding sessions

7) Enforcement :

a) Violations of this agreement must be reported by team members and handled atthe lowest level possible (i.e. solved internally without faculty assistance)

b) Team members will exhaust all possible means to ensure compliance

c) If the team is unable to resolve these issues, an appointment must be made withProf. Buckley to discuss the problem; at a minimum an email must be sent oncesuch a problem has been recognized

SrumScum

Rules and Expectations

As an individual I am expected to:

• Attend all meetings and commitments previously agreed to and scheduled baring emergencies/work obligations with at least 24 hour notice.
• Any problems found during development will be made apparent to the group.
• Be mindful and treat other team members with respect.
• Work delegated will be assume to be completed on time, else notify the team immediately.
• Review with team and professionally moderate any client communication.
• Online communication is preferred.

As a team we are expected to:

• attend meetings
• participate
• meet with faculty advisor
• attend schedule meetings

FusionContract Rough Draft

As an individual I am expected to:

-Attend all meetings and commitments previously agreed to and scheduled baring emergencies/work obligations with at least 24 hour notice.

-Any problems found during development will be made apparent to the group.

-Be mindful and treat other team members with respect.

-Work delegated will be assume to be completed on time, else notify the team immediately

-Review with team and professionally moderate any client communication.

-Online communication is preferred.

As a team:

-attend meetings

-participate

-meet with faculty advisor

-attend schedule meetings

SB6

Purpose

The purpose of this document is to outline and define some of the policies, procedures, and expectations each member of Team SB6 shall hold themselves and the other members of the group accountable to. This document is not intended to be a comprehensive list of policies, procedures, and expectations, merely those deemed most important.

Any email communication that need to be sent to all group members should be sent to the above email address, where the message will be forwarded to all team members.

Team Meetings

Each team member shall attend all team meetings in a punctual manner. If a team member is unable to attend a meeting, that member shall notify the group as soon as reasonably possible, preferably prior to the meeting start time.

Weekly team meetings shall follow an agenda created by the team in advance of each meeting. This agenda shall be created by brainstorming potential topics by the entire team and finalized by the meeting Facilitator the day before the meeting. During the meeting, the Facilitator shall keep the focus of the meeting on the topics outlined on the agenda for that meeting. Each team meeting shall have minutes recorded and stored for review by a Secretary. The meeting roles of Facilitator, Secretary, and any other deemed necessary shall be rotated on a weekly basis, as defined by a schedule to be created on the first official team meeting.

Team Member Behavior

• All team members shall show respect to and maintain a civil decorum towards other team members and respective skill level.
• If a team member does not know what to do or how to do a particular task, that team member is expected to ask the group for help.
• If a team member commits to a particular task, that member is expected to complete the task on time, or notify the team of any problems that affects their ability to complete the assigned task as soon as possible.
• All team members are expected to attend all team meetings or provide prior notification to the entire team of any absences, barring an emergency.
• Any communication with the client shall be copied to all members of the team by also addressing the communications to the group email list address.
• Any issues the team or individuals have with any member of the team shall first be discussed within the group during the next team meeting. Only if the team is unable to satisfactorily resolve the issue within a reasonable time-frame shall the team notify the faculty advisor of the problem.

Occupied Software Team Conduct

Sprints Specific Responsibilities
Determine Requirements for Sprint
Product backlog maintenance
Design
Flow charts
Implementation
Testing and Integration / Other Responsibilities
Client liaison
Advisor liaison
Buckley liaison
Meeting facilitator
Agenda creation
Location reservation
Meeting scribe
Meeting chair
General researcher

Team Expectations

• Good communication is expected. If someone cannot make a commitment, 24 hours advance notice should be given unless there is an emergency or a situation arises in which 24 hours notice cannot be given. Even if there is only a chance of the situation occurring, the team should still know. This notice should be given in either our Groupme or group email account so that every member is aware.
• Good and prompt communication is expected, but responses do not need to be immediate. Responses can be delayed by a few hours, but should occur within the same day.
• Everyone is responsible for the stories they take on. If people are encountering difficulty with their given stories or tasks, they should let the rest of the team know at the time of the problem and not at the last second. This will enable the team to find ways to assist, and maintain transparency.
• If a task is not completed successfully in a sprint, but notice was given to those not handling the task, the other team members will recognize that an effort was made.
• Respect others options. Be willing to have rational discussions about issues brought up. No ideas should be immediately dismissed.
• For design, multiple members should be present when discussing program flow before implementation. This includes members not taking on the task for this sprint.
• Unless a person brings up a problem, we trust team members will accomplish their tasks.
• All members are expected to attend all client and advisor meetings, as well as the weekday team meetings. Weekend meetings are optional by default.
• For responsibilities which cannot be divided among multiple members, we will cycle these tasks in a round robin manner each sprint.
• The person taking on the role of the meeting chair for a given sprint must not be the person taking on the role of the meeting facilitator. The facilitator is in charge of setting up the agenda, location and other meeting details while the chair is in charge of ensuring that the agenda gets covered in the meeting.
• The person taking on the role of the meeting chair shall handle the meeting templates, since those are primarily used to steer the meetings.

• The person taking on the role of the meeting scribe will, in addition to recording meeting minutes, type up the minutes and store them on the Google Drive for future reference.
• No single person will be in charge of one single aspect of the project (ex. Code, documentation, external communication), but if a person has expertise in a given area, they should be willing to provide advice.
• Under no circumstance shall politics be discussed.

Conflict Management

A conflict is any occurrence not addressed in this document that three people agree to be a conflict. Conflicts should be brought up to the team at the time it is determined to be a conflict, and will be addressed in the next team meeting if not addressed prior. These conflicts will be addressed immediately at the start of a meeting, as the first agenda topic. A set amount of time will be given to resolve the conflict, and if this is not sufficient, we will contact Professor Buckley for his advice.

Infinity ∞

Meetings:

1. Meetings will be held regularly every week on Thursday at 3:00 PM until 4:00 PM.

a. All members will be in attendance. Any member who can not attend will notify thegroup through the group’s primary mode of communication. (See below.)

b. Team Meetings will be held as needed before the scrum process begins.

2. Meetings with the client and with the scrum master are mandatory.

a. At client meetings, all members will present themselves professionally, includingbehavior, dress, and cleanliness.

3. Before each meeting, an agenda will be drafted and agreed upon by the entire team.

Group Communication:

1. Group communication will be done primarily through Google Chat.

a. All members will have Google Chat installed on their phone for promptcommunication.

b. Group text messages will be the secondary form of communication.

c. Email will be the third form of communication with every member of the teamincluded in the CC block.

d. Phone calls will not be made as there is no way to include everyone in that formof communication.

2. Group members will accurately and clearly communicate what they believe they canaccomplish and what their skills can entail.

3. During scrum meetings, work will be delegated among team members evenly, withrespect to member’s skills and specialties.

4. Members will keep the rest of the team updated with progress status, and any issues that may arise.

Buddha myToast

Contract

Expectations of one another

• Respectfulness
• Professionalism
• Punctuality

Expectations of the team

• Each sprint must have a goal
• Stay focused on goals
• Make sure daily goals are clear
• Make decisions together
• Keep project logs for clients
• Maintain constant communication
• One meeting a week at least
• Transparency and honesty

NO CELLPHONES or LAPTOPS during meetings!

Null Reference Exception

Expectation of one another:

• Finish work assigned to you in a timely manner.
• Present and on-time for meetings unless otherwise discussed.
• If struggling, ask for help right away or let the team know.
• If you are going to be late, notify others.
• Peer review each other's work.
• Be respectful of team decisions.

Expectation of team:

• Collaborate and Cooperate.
• Try to finish all the project requirements to the best of our ability, while maintaining a good design.
• Stay on topic in meetings.

Wild Cats

Expectations:

• Be honest
• Be respectful
• Try to contribute
• Don’t be afraid to ask for help
• Ask if other team members need help
• Own up to mistakes
• Let team members know if you cannot be present
• Try to attend team meetings on time
• Complete work assigned in a timely manner

TEAM PENTAKILL

Our team agreement:

• We will meet at least once a week.
• Our meetings will always have an agenda.
• We will check group chat every day.
• All team members should attend client meetings.
• Work should be reviewed by at least one other member.
• Ask for help, always.
• We will use Git for code check-ins.
• Codebase must have a minimum of 80% code coverage.
• We will write maintainable code.
• We will practice open communication between members.
• We will trust, but verify.
• We won’t commit ourselves to work we can’t finish in a sprint.

Our team email is

C Hex

1. Communication is essential and is a key part of most other rules.
2. We will have a positive attitude.
3. We will always be honest.
4. We will always be on time, have an agenda ready, and turn off distractions, for team meetings.
5. We will make decisions that are approved by the entire team.
6. We will not interrupt one another and let the person finish with what they’re saying.
7. We will be accountable to our commitments.
8. We will always be transparent with one another.
9. We will raise issues/questions early.
10. We won’t be afraid to say “I don’t know.”
11. We will always try to help one another.
12. We will check communications like email regularly.
13. We will be clear about who is responsible for completing a task.
14. We will respect one another’s opinions and ideas.
15. We will attend all meetings if possible.
16. We will contribute similar amounts to the project.
17. We will complete tasks within a reasonable timeframe.
18. We will communicate about the progress of the task we are responsible for.
19. We will not make assumptions and always ask for clarification.
20. We will work together and try not to do too much on our own.
21. We will make sure to participate in discussions.
22. We will keep each other informed.
23. We will have fun!

/ BACKSLASH

Expectations of Each Member:

1. Everybody is expected to complete the task that was assigned to them.
2. Everybody is expected to meet in person. If they’re unable to meet, they’re expected to inform the group of their absence early on.
3. Members should not agree to commit to a task if they know they cannot complete it.
4. All members must be on time to meetings with the team, client, and faculty advisor.
5. During meetings, a clear agenda should be created so that no time is wasted during each meeting.
6. Everybody should be working together to agree on any solution to a problem.
7. If changes to agreed upon work is altered, all team members must be notified of the changes.
8. Decisions should never be made individually, but as a team.
9. The team should decide which duties fit each person the best and assign the work as evenly as possible.
10. If you’re unable to do a certain task, it is expected of you to find another way to contribute to the team.
11. If you have a problem, speak up early on so that the problem can be addressed early on and a solution can be devised.
12. Everybody should always be communicating with each other to ensure that everyone is update with the progress of the project.
13. Each member is expected to following a strict coding guideline to ensure that everyone understands the code fully.
14. Meeting times are to be planned in advance to ensure that all members can attend the meeting.
15. Each sprint should be planned out carefully in a way that the requirements for DONE can be achieved.

This contract is always subject to change when agreed upon by all members of the group. The most recent version of the contract will always be used. Team 14 Contract version 2, last updated 7:39 AM, 2/28/17

MANDATORY SOLUTIONS

1)Show up to client meetings prepared and ready to work with all necessary tools and information for the meetings(24hrs notice if unavailable, emergency exception).