For this initial exploration into what you bring to a team, try to avoid thinking about your TECHNICAL skills. Your answers to these questions should apply to any project/team that you work on:
How would you describe your preferred working style?
- Ivonne - likes to work independently but wants to collaborate big time on planning stages.
- Colgan - flexible - willing to work independently or together as needed.
What strengths do you bring to a team?
- Ivonne - honing in on the most important things, planning, taking tasks one at a time as required, more into Javascript than HTML or CSS.
- Colgan - planning, organization, very similar strengths to Ivonne ^^^
How do you prefer to handle disagreements that come up? Trust me, they will come up!
- Ivonne - wants to make sure to give team mates the space to learn and make mistakes if necessary. Wants to be communicative about decisions and be willing to talk out disagreements with teammates.
- Colgan - wants to be able to talk out any disagreement with his partners, doesn't want to have an unnecessary conflict over minor issues that can be avoided, nothing is worth blocking the progress on the project or our learning.
How do you communicate best? What tools do you need to communicate well with your teammates?
- Ivonne - slack, video chat
- Colgan - slack, video chat
How do you prefer to make decisions as a team?
- talk everything out, be good and kind to each other. Don't be afraid to offer suggestions or alternative ideas for issues.
What scheduling constraints do you have? What are your preferred work times outside of normal school hours?
- Ivonne - Available during class time, generally cutting off around 7PM MST on most days.
- Colgan - takes an hour to do exercise after class every day. Generally does not want to work past 9:30 MST. Available during regular class times on weekends.
How do you prefer to receive feedback? How do you prefer to give feedback?
- Ivonne - super cool with alternative suggestions to her code, willing to receive any feedback, wants to give feedback a chance to set in to understand it fully.
- Colgan - try your best to be nice please, but honest feedback will only make me better. Don't be afraid to offer helpful suggestions and good faith criticism.
How do you want the group to solve problems when members run into blockers on the project?
- struggle for about an hour, any longer than that its time to ask for help.
What is our GitHub WorkFlow/Process?
- don't merge into main without notifying our partner for review
- try our best to be generous and granular with our branches
- always use a PR template
- atomic commits, commit on successful functions and other small adjustments.