What are the key strengths of each person on the team?
Marie - google fu
Matt - active listener, collaborator, detail-oriented
Aloysious - Markdown nerd, Good at seeking support
Tony - team player, good listener, problem solver.
How can you best utilize these strengths in the execution of your project?
- Collaboration
In which professional competencies do you each want to develop greater strength?
Marie - developer tools
Aloysious - Handling ambiguity
Matt - Coding knowledge, technical understanding & communication
Tony - functions, algorithms and git flow.
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?
Review the day’s tasks together, pair and mob programming.
Walk through, pull request & merging explanations
Your team should agree on a process for handling disagreements, should they arise. It is better to have a plan in place ahead of time so you can all refer back to it when necessary.
Describe at least: What will be your group’s process to resolve conflict, when it arises?
- Be adults = Communicate
What will your team do if one person is taking over the project and not letting the other members contribute?
- Open, organic conversations. Accept constructive feedback
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?
- Pair/mob program and review code
How will you raise concerns to members who are not adequately contributing?
- Talk to each other to find out what’s blocking development.
How and when will you escalate the conflict if your resolution attempts are unsuccessful?
- Seek a third party if all else fails
Before beginning to tackle the project, determine how your group will communicate with each other. This is not an individual effort. Make sure everyone feels comfortable with the identified methods of speaking up.
What hours will you be available to communicate?
- Class hours.
What platforms will you use to communicate
- Slack, email. phone.
How often will you take breaks?
- Hourly check-in’s when we are co-working to take breaks
What is your plan if you start to fall behind? -Get help from TA, work on days off.
How will you communicate after hours and on the weekend?
- Slack is the primary method of communication
What is your strategy for ensuring everyone’s voice is heard? Intentionally creating space for each person to throw ideas into the pot. How will you ensure that you are creating a safe environment where everyone feels comfortable speaking up? Practice psychological safety
Explain your work plan to track whether everyone is contributing equally to all parts of the project, and that each person is working on “meaty” problems. This should prevent “lone wolf” efforts and “siloed” efforts.
How will you identify tasks, assign tasks, know when they are complete, and manage work in general?
- Trello / breaking down features and tasks will allow us to see where we are at and who is working on what.
What project management tool will be used?
- Trello / slack
What components of your project will live on GitHub?
- Front end Application & Backend server
How will you share the repository with your teammates?
- Permissions for collaborators
What is your Git flow?
- Dev branch for quality control / re-deployment
- From main : Git pull origin main { as a group }
- Create branches for individual features
- Communicate prior to the start of each day which branches / features are being worked on to avoid “gituations”.
Will you be using a PR review workflow? If so, consider:
How many people must review a PR?
- At least one other person
Who merges PRs?
- Reviewer or other group member
How often will you merge?
- Daily or as we see fit
How will you communicate that it’s time to merge?
- Speak in remo or slack