Skip to content

Instantly share code, notes, and snippets.

@kimmccaskill
Created December 12, 2019 22:45
Show Gist options
  • Save kimmccaskill/1c5d26e0b3dcd707754103a818e81402 to your computer and use it in GitHub Desktop.
Save kimmccaskill/1c5d26e0b3dcd707754103a818e81402 to your computer and use it in GitHub Desktop.
### Guiding Questions to Define The Relationship:
Project: 1909 Mod 2 Group Project
Group Member Names: Cody Smith, Jim Weist, and Kim McCaskill
* What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
CS: Collaborate as much as possible, JW: Divide up smaller pieces, KM: Paired/DN for setup/structure
* How do you communicate best? How do you appreciate receiving communication from others?
CS: Open communication and trying different things, JW: In person or slack, doing what we need to do to build up communication, KM: Open honest feedback
* How would you describe your work style?
KM: Goal oriented, CS: Time-table, JW: Planned out work
* What are each of our strengths? How can our strengths complement each other?
CS: Helping determine and plan next steps/goals, JW: Design and jQuery, KM: Can fill in gaps when needed.
* What’s gone well or poorly in your previous projects?
CS: Done well in communication whether remote or in person, JW: Don't prefer loud environments, KM: Understanding everyone
's code
* How will we set direction and make decisions as a team?
CS: Setting up time-oriented goals early, KM: Revisiting goals based on progress, JW: Discuss direction and priorities
* What do you need (resources, environment, communication) to do your best work?
JW: Quieter environment, CS: Quieter environment as well, KM: POMS
* What scheduling restraints do you have? What are your scheduling preferences?
CS: Tuesdays would like to get out earlier and prefer minimal work on weekends, JW: Earlier bird and prefer not to stay past 6P, KM: Thursday evenings go climb and minimal weekends
* What is your style for giving feedback? Does anything ever hold you back from giving feedback?
CS: Spit out feedback, JW: Constructive, KM: Be kind
* How do you want the group to solve problems when members run into issues with features of the project?
Myself > Partner > Rocks > Mentor > Instructor > Cry/Sleep on it > Blackout > Smash macbook
* How do you know if a project is successful? How can we achieve that as a group?
CS: Bug free code, JW: Learning goals with target 3 score, KM: When we are excited to show it to others outside of Turing
* How will we recognize each other's successes and celebrate them?
KM: Fist bumps and high fives, CS: Hugs and kisses, JW: High fives with no kisses or hugs
###Team strengths & collaboration styles (consider discussing your Pairin qualities here):
How we can use our strengths to overcome obstacles:
KM/JW/CS: Communicate problems and don't be afraid to ask for help, CS: Positivity and not getting overwhelmed
What do you need to look out for, in terms of strengths/working styles coming into conflict?
CS: Conflict will probably happen. Use open communication to get past it. JW: Get used to each others working styles to come together. KM: See conflict as an opportunity for growth
Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
M/W try to work together. T/Th optional. This schedule is flexible. Nobody is expected to stay after 6P
What is the one hour/day that each teammate has on their calendar for personal study/practice time?
T/TH and weekends
Additional Notes:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment