Team-Agreement

Cooperation Plan

1. Knowing that every person in your team needs to understand all aspects of the project, how do you plan to approach the day-to-day work?
   • we are planning to divide the work so everyone can work on both the frontend and the backend and before we divide the work we will discuss every task.

Conflict Plan

1. What will be your group’s process to resolve conflict, when it arises?
   • Give everyone the time and opportunity to present their own perspective on events and to respond to any criticism.
2. What will your team do if one person is taking over the project and not letting the other members contribute?
   • we will discuss why the member is taking over the project and try to figure it out
3. How will you approach each other and the challenges of the project knowing that it is impossible for all members to be at the exact same place in understanding and skill level?
   • we will do pair programming to make a brainstorming and to make up for each other weaknesses
4. How will you raise concerns to members who are not adequately contributing?
   • talk to him alone and better understand his motives and try to make him understand the problem
5. How and when will you escalate the conflict if your resolution attempts are unsuccessful?
   • If it started to affect the team performance

Communication Plan

1. What hours will you be available to communicate?
   • mainly from 10am to 5pm.
2. What platforms will you use to communicate (ie. Slack, phone …)?
   • Slack, Remo, Zoom
3. How often will you take breaks?
   • we will take a 1 hour break once and maybe 10 min few times
4. What is your plan if you start to fall behind?
   • we will incraese the work time.
5. How will you communicate after hours and on the weekend?
   • we will use Slack.
6. What is your strategy for ensuring everyone’s voice is heard?
   • listen to everyone and discuss their opinion
7. How will you ensure that you are creating a safe environment where everyone feels comfortable speaking up?
   • by not neglecting an opinion and ask about what they think

Work Plan

1. How you will identify tasks, assign tasks, know when they are complete, and manage work in general?
   • we will divide every feature into two tasks one for the backend and one for the frontend.
2. What project management tool will be used?
   • trello

Git Process

1. What components of your project will live on GitHub?
   • everything
2. How will you share the repository with your teammates?
   • by creating an organization and invite them
3. What is your Git flow?
   • creating a new branch for every task and creating a staging branch to make sure everything is merged correctly before merging to the main branch
4. How many people must review a PR?
   • we will review them in meetings
5. Who merges PRs?
   • we will merge them in meetings
6. How often will you merge?
   • after a new task is finished.
7. How will you communicate that it’s time to merge?
   • on slack or after the meeting