PREP.md

Traveler's Quill

Project Prep

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

Emily - Backend building servers and databases. Godlike CSS Skills. Josh - Talking through algorithms, good understanding of concepts. Awesome support, teamplayer, hype-train Christina - Top tier organization and communication skills, detail oriented and debugging skills

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

Emily - Backend building servers and databases Josh - Support teammates. create things Christina - Catch errors and debug problems

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

Emily - Craft competency Josh - Looking to grow in software knowledge Christina - Craft competency

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?

Team meeting, decide tasks, execute. Communicate with eachother when it comes to dividing tasks and pushing up changes to gitHub

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

Open communication and being curtious, if someone begins to feel frustrated they can call for a 5 minute break and we can come back ready to solve any issues. If problems escalate, call Sara to mediate.

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

Voice if you feel you're not contributing enough. We can take a couple of minutes every hour before a break to debrief and make sure everyone is feeling good about the workflow.

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?

Help eachother understand, call a TA or Sara if it is not working out explaining.

How will you raise concerns to members who are not adequately contributing? How and when will you escalate the conflict if your resolution attempts are unsuccessful?

• We can take a couple of minutes every hour before a break to assess where we're at and if there are portions of the project that need attention we can voice that the person who is contributing the least take over those parts of the project. If the issues continue to where it is hindering the progess of the project, then let Sara know.

What hours will you be available to communicate?

Daytime hours - No Sundays

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

Slack, text

How often will you take breaks?

10 minutes every hour, 5 minutes when needed if we are getting frustrated.

What is your plan if you start to fall behind?

Work harder, plan better and allot time outside of class to catch up. Re-assess time management

How will you communicate after hours and on the weekend?

Text, slack

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

At each 10 minute break, take a couple of minutes to assess where we're at, debrief, everyone gets a chance to say anything they feel they need to say.

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

Check in with eachother, make sure everyone is feeling heard.

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

outline the project, dig deeper into the components of the project, list tasks and pick/choose. keep proper git-flow.

What project management tool will be used?

Trello (figma for a visual)

What components of your project will live on GitHub?

All components

How will you share the repository with your teammates?

made an organization on github and we are all admins

What is your Git flow?

good communication - ACP often and verbally communicate when we are doing it, pull before working.

Will you be using a PR review workflow? If so, consider: How many people must review a PR?

we will have main branch protection, but anyone can complete pull requests.

Who merges PRs?

individuals push to their branches

How often will you merge?

We'll have portions of the project split between three people, when each person is done with their portion they will push and once everyone's portions are pushed up we will merge to test and then to main

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

sound the alarms