This is the frontend side for a project that shows analytics and visualizations for a user's gmail account.

• User stories
• Requirements
• Wireframe
• Domain model and Schema

Alphabetically by last name: Miguel Fierro, Jordan Folk, Joseph Nguyen, Chloe Nott, K'lan Stovall

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

  • Chloe: Detail oriented, goal focused
  • K’Lan: Back-end and front- end knowledge and debugging
  • Joseph: Debugging and Back-end
  • Jordan: Backend, briefing/presentation skills
  • Miguel: time-management, front-end

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

  • Use our strengths to complement each other’s weaknesses.

• In which professional competencies do you each want to develop greater strength?

  • Chloe: I would like to work on my collaboration competency.
  • K’Lan: Analytical Thinking
  • Joseph: Communication
  • Jordan: Handling ambiguity
  • Miguel: problem solving

• 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?

  • Daily standup meeting in the morning to assign tasks (see Trello below).
  • Communicate frequently.

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

  • Escalate issues if can’t resolve amongst ourselves.
  • Taking a break to let emotions subside
  • Have a mediator
  • Communication preferences for conflict resolution, voice is generally fine, slack is okay too.

• What will your team do if one person is taking over the project and not letting the other members contribute?

  • Escalate issues if can't resolve amongst ourselves
  • 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?

• Working together to help each other. Pair programming, live view, remo, etc.

  • How to avoid letting some people get crumbs: try to pair program, try to distribute load between members, make sure there’s at least two people for huge features

• How will you raise concerns to members who are not adequately contributing?

  • Escalate issues if can't resolve amongst ourselves

• How and when will you escalate the conflict if your resolution attempts are unsuccessful?

  • Escalate as needed by the next day if resolution can’t be found.

• What hours will you be available to communicate?

  • 9 am - 6 pm core hours. More is okay too.

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

  • How often will you take breaks?

• Ideally every hour. If anyone needs a break just take a break.

  • What is your plan if you start to fall behind?
  • Adjust plan so that an MVP product can be completed.

• How will you communicate after hours and on the weekend?

  • Slack.

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

  • Give everyone an equal chance to speak.

• How will you ensure that you are creating a safe environment where everyone feels comfortable speaking up?

  • Any topic is okay to talk about.

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

  • Standups to identify and assign tasks.
  • 9 am standup with Sara/Hexx.
  • Trello will be used to manage the work and completed tasks.

• What project management tool will be used?

  • Trello for project management.

• What components of your project will live on GitHub?

  • Front-end and Back-end

• How will you share the repository with your teammates?

  • Everyone will be in an organization

• What is your Git flow?

  • Every person has a branch for their task
  • Push to Staging Branch at the end of the day and compare before merge

• Will you be using a PR review workflow? If so, consider:

  • How many people must review a PR?
  • 2 to main.
  • 1 to staging.

• Who merges PRs?

  • Any team member can merge, provided 1 or 2 other team members approve.

• How often will you merge?

  • Every day at a minimum.
  • After every feature completion ideally.
  • At least every morning and evening, with flexibility for additional. Communicate with others if new pulls are needed.
  • Git stash -> git pull -> Git stash pop

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

• Let everyone know in slack or reemo before a merge.