One teammate should copy and paste the raw markdown into a gist of your own.
- What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
- How do you communicate best? How do you appreciate receiving communication from others?
- How would you describe your work style?
- What are each of our strengths? How can our strengths complement each other?
- What’s gone well or poorly in your previous projects?
- How will we set direction and make decisions as a team?
- What do you need (resources, environment, communication) to do your best work?
- What scheduling restraints do you have? What are your scheduling preferences?
- What is your style for giving feedback? Does anything ever hold you back from giving feedback?
- What do you identify as being your biggest strength(s) technically? Where do you feel you could use improvement in your technical skills? How can our team help support you in improving these skills?
- How do you want the group to solve problems when members run into issues with features of the project?
- How do you know if a project is successful? How can we achieve that as a group?
- How will we recognize each other's successes and celebrate them?
Any additional questions that you would like to add:
Project: 1911 Mod 2 Pair Project
Group Member Names: Tim Nguyen and Olivia Webster
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? YES, you can still fully answer this question without knowing exactly what you're going to build.):
Tim: expectation: work mostly together driving and navigating and complete up to iteration 5. Open communication between team. goal: Try to get better understanding of concepts for this project so that I can implement them in future projects. Finish the project in a timely manner. how will we know success: I will feel successful when the project is completed and make we both understand everything. No lingering questions.
Olivia: all of the above. expectations: I would like to front load a lot of the work so that if we get hung up on things, which I'm sure we will, we have time to solve them without having to panic at the end. goal: would like to get better with making multiple classes talk to each other while implementing DOM manipulation. how will we know success: when I feel like I have a good grasp on the concepts and am not panicked about getting the project completed. When we both have similar numbers of commits.
Team strengths & collaboration styles (consider discussing your Pairin qualities here): Tim and Olivia are both very flexible and willing to adjust schedules. Tim is kind and patient. Olivia is also patient. Both always willing to help. Both try not to get negative.
How we can use our strengths to overcome obstacles: Patience to spend a lot of time sitting in the struggle. Olivia is pretty good at asking for help. Tim wants to practice reaching out for help. What do you need to look out for, in terms of strengths/working styles coming into conflict? Olivia is anxious about feeling a bit behind, so needs to be honest about that. We will both be open communicators. Tim will sometimes need to leave by 7pm for personal reasons. But will do his best to accomodate working late if needed. Schedule Expectations (When are we available to work together and individually? What constraints do we have?): after school for a few hours at least all day on saturday and sunday. Olivia would prefer not work past 9:30pm
What is the one hour/day that each teammate has on their calendar for personal study/practice time? Tim: this project takes priority, so will work on JS Fun when he has time, but is not going to schedule that time. Olivia: I'd like to work on JS fun in the morning before class and for an hours on sunday. Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?): Every day on slack and github via pull requests. Being responsive to messages. And talk in person before class and on poms/ during lunch.
Abilities & Growth Expectations (Technical strengths and areas for desired improvement): Olivia: would like to get a better grasp on using classes together and writing tests. Tim: would like to get better at using technical vocabulary to describe things and how they work. Get better at using classes together effectively.
Expectations for giving and receiving feedback: Olivia: direct but kind and specific. Tim: being respectful to each other. Don't be rude.