Project: CuraTour
Group Member Names:
- FRONTEND: Kristen Bair, Richard Tyler, Kevin Hartmann, Drew Bradley
- BACKEND: Phil McCarthy, Robert Heath
Goals and Expectations for the Project (What does each group member hope to get out of this project? What do we want to achieve as a team? How will we know that we're successful?): TECH:
- FE: React Hooks and Context API, possibly PWA
- BE: Ruby on Rails
Team strengths & collaboration styles (consider discussing your Pairin qualities here):
- Kevin: Communication. Enjoys to talk and will do it a lot.
- Richard: Over communication is better than under communication. Make sure we're on the same page. Decision maker.
- Kristen: Organization and planning. Collaboration and flexible in decision making. Direct when addressing problems.
- Drew: Goal oriented. Problem solver. Ideas. Willing to try new things.
- Robert: Diffusive thinking. Planning.
- Phil: Systems architecture and design. Big picture. Great at explaining. Consistent communication.
How we can use our strengths to overcome obstacles:
- Kristen: Direct and always willing to find a solution.
- Richard: Talk it out.
- Kevin: Adaptability. Go with the flow. Adjust to decisions.
- Drew: Boudaries. Refer back to DTR and group agreements, but understand that things change.
- Phil: Reviewing code and helping with attention to detail.
- Robert: Remind us to take breaks. Step back and think it out.
Schedule Expectations (When are we available to work together and individually? What constraints do we have? Make sure to discuss the remote questions above in regards to this section):
- Flexible schedule. Asynchronous workflow. Paired programming. Shared calendar.
- Evenings are async.
- Stand ups during asigned class work time.
Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team? How will we communicate about our emotional and mental well-being with each other?):
- Slack channel. Daily retros/standup on zoom.
Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
- BE/FE crossover. Working on a full stack team.
Workload Expectations (What features do we each want to work on?):
- Equitable workloads.
- Group members will work on assigned issues.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
- Project Board.
- Issue templates.
- Custom labels.
- Milestones. Linked to issues and have timeline.
- PR template.
- PR reviewed in timely manner.
Pomodoro Break Schedule:
- When needed. 45 on/ 10 off.
Expectations for giving and receiving feedback:
- Direct and actionable.
- Positive feedback is important.
Additional Remote Considerations:
- Robert is in Texas. 1hr ahead of MT.
Project management tools we will use (GitHub projects or Trello are popular tools):
- GitHub projects
- Slack channel - respond in thread. Group chat if needed.
- Miro - Wireframing, ERD, data flow.
- Repl, Google Docs, Sheets, etc. will be shared on Slack channel.
Day 1 Agenda:
Additional Notes: