Skip to content

FaceRecognition-Attendance-System/Team-Agreement

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

9 Commits
 
 

Repository files navigation

FaceRecognition-Attendance-System

Team Members

-Ahmad Jaara

-Barham Farraj

-Eman Al-shaikh

-Faisal Al Hawajreh

-Raneem Oqaily

-Zaid Jarrar

Cooperation Plan

  • What are the key strengths of each person on the team?

    • Barham Farraj: Debugging, pure python.

    • Ahmad Jaara: Data science, on the clock, team player.

    • Eman Al-shaikh: Computer vision, punctional.

    • Raneem Oqaily: Web scraping, researcher skill, data science.

    • Zaid Jarrar: Data science, pure python, web scraping.

    • Faisal Al Hawajreh : Attention to detail,analytical thinking.

  • How can you best utilize these strengths in the execution of your project?

    • We divide the tasks based on what we are good at.
  • In which professional competencies do you each want to develop greater strength?

    • All of us agree on improving on machine learning and computer vision fields.
  • 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?

    • By using a project management tool (trello), in addition to having brief discussion at the beginning of each day.

Conflict Plan

  • What will be your group’s process to resolve conflict, when it arises?

    • Dedicate a time to discuss any conflicts between members and to find the solution around it.
  • What will your team do if one person is taking over the project and not letting the other members contribute?

    • we will let the member understand the situation.
    • We will work it out together.
  • 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 explain the idea thoroughly to the team.
    • We will plan an extra meeting to do further revision of the current idea.
  • How will you raise concerns to members who are not adequately contributing?

    • We will let the member understand the situation.
    • We will distribute the tasks accordingly
  • How and when will you escalate the conflict if your resolution attempts are unsuccessful?

    • We will contact the teacher assistant.

Communication Plan

  • What hours will you be available to communicate?

    • 10 AM - 2 PM

    Any extra meeting will be discussed during the day.

  • What platforms will you use to communicate (ie. Slack, phone …)?

    • Slack.
    • Discord
  • How often will you take breaks?

    • Every 1 hour we will take a 10 mins break.
  • What is your plan if you start to fall behind?

    • We will an make extra meeting to discuss the time needed to accomplish the (MVP)
  • How will you communicate after hours and on the weekend?

    • Mainly on discord
  • What is your strategy for ensuring everyone’s voice is heard?

    • Try to let everyone give an idea.
    • Keep asking team members if we are all in agreement.
    • Specify the first 15 mins for everyone to share their experiment from the last task or any new ideas & feedback at the end.
  • How will you ensure that you are creating a safe environment where everyone feels comfortable speaking up?

    • Accept any new ideas given and never underestimate it.
    • Make space for open & equal discussions.
    • Not judging anyone for their opinion,after all we are all learning.
    • Have faith in eachother.

Work Plan

  • How will you identify tasks, assign tasks, know when they are complete, and manage work in general?

    • After every Meeting session the tasks will be identified.
    • The tasks will be assigned based on strengths of every team member.
  • What project management tool will be used?

    • Trello

Git Process

  • What components of your project will live on GitHub?

    • Documentations
  • How will you share the repository with your teammates?

    • The repository will be on published the organization for the group.
  • What is your Git flow?

    • Every main part of the project should have a separate branch.
    • Make A new main branch for testing purposes.
  • Will you be using a PR review workflow? If so, consider:

Yes,Once a task completed a meeting will be hosted to discuss the PR content.

  • How often will you merge?

    • Once every section is completed a merge will be done to the testing branch.
    • Every version of the project will be merged from the testing branch to the main.
  • Who merges PRs?

    • Team Leader
  • How will you communicate that it’s time to merge?

    • After a revision of the PR with the team.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published