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 1 Pair Project
Group Member Names:
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.):
Tanisha: Wants to be able to be able to write really good tests as a personal goal. Wants to learn new technologies well enough to be able to replicate on another project. It would be a success if we not just finish the project but understand each aspect individually fully enough to explain it well. Kim: Wants to get experience refactoring and using jQuery As a team I want to get really good with work flow and have good grasp on github. Olivia: I really want to learn jQuery and get comfortable with the api stuff. For everyone to be able to voice opinion and be heard and understand what is happening. We'll be succesful by having a good work flow and being able to stay on a good schedule.
Team strengths & collaboration styles (consider discussing your Pairin qualities here): Kim: likes to work closely together. Strengths - communication, work ethic, and willingness to try things Olivia: also like closely. generally do what i say i am going to do. I'm not afraid to ask questions. Tanisha: tanisha is organized. good at breaking down big things into small pieces. mixed collaboration style. Likes to work together in the beginning but also alone. wants practice working remotely.
How we can use our strengths to overcome obstacles: patience, communication, tenacity, not being ashamed to ask for help our strengths balance eachother. We are all good communicators, so are able to talk through problems. patience with each other.
What do you need to look out for, in terms of strengths/working styles coming into conflict? being mindful to everyone so that they have space to work in ways that fell most comfortable for them. make sure no one feels left out of the process.
Schedule Expectations (When are we available to work together and individually? What constraints do we have?): Kim lives far away in the south and has a long commute. light rail gets shady after 7 so probably want to leave prior 7. is available most weekends. Tanisha doesn't work satudays at all. Tuesday feb 18th jcs at 5pm and meetup after so can only work until 5. ideally end time of 6:30 7pm. Olivia: not available the 15th, 19th birthday wants to do dinner.
What is the one hour/day that each teammate has on their calendar for personal study/practice time? Tanisha: saturday off limits, mornings for personal work, kim: morning Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?): Almost every day on slack.
Expectations for giving and receiving feedback:
Tanisha: non-violent communication, likes feedback often direct but kind and specific We are going to have retros
Safe space: everyone is very receptive to feedback specific feedback
Additional Notes:
Retro schedule: 2/18: 2pm 2/21: 12pm 2/24: 1pm 2/26: 1pm