Skip to content

Instantly share code, notes, and snippets.

@cgeglio
Last active October 7, 2019 20:40
Show Gist options
  • Save cgeglio/2b0f0dc646d58cf985e4a6b21b88a9b7 to your computer and use it in GitHub Desktop.
Save cgeglio/2b0f0dc646d58cf985e4a6b21b88a9b7 to your computer and use it in GitHub Desktop.
Virginia & Carla

Carla & Virginia DTR Project: Paired Project #1

Group Member Names: Carla & Virginia

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?):

Not only learning technical skills but also improving communication skills. We want to create cohesive solutions instead of one-sided answers. We will feel successful if we have a project we're proud of at the end.

Team strengths & collaboration styles (consider discussing your Pairin qualities here):

We are both task-oriented and like to get things done. We are both more divide-and-conquer people, assuming we have a very thorough plan/foundation.

How we can use our strengths to overcome obstacles:

We are both big on communication which should help us overcome most obstacles. You can't communicate too much!

Schedule Expectations (When are we available to work together and individually? What constraints do we have?):

We are both flexible and available to stay after school to work together. Open to meeting an hour before class for retro.

Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):

Can't communicate too much. A morning retro will be really useful. Big ideas should be in person- so that we can draw things out, write pseudo code, etc.

Abilities & Growth Expectations (Technical strengths and areas for desired improvement):

Attention to detail is one of my strengths. Virginia has some coding experience which will come in handy. I would like to improve my muscle memory. Virginia would like to get better at articulating what the code is doing.

Workload Expectations (What features do we each want to work on?):

We would like an equal split so that we both have exposure to everything going on in our code.

Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):

Review the process together and in class. (Certain parts haven't been covered yet... branches, etc.)

Expectations for giving and receiving feedback:

Open to positive and negative feedback. Honesty>Ego!!!

Project management tools we will use (GitHub projects or Trello are popular tools):

Mainly GitHub

Day 1 Agenda:

Stay after school to talk about our project once it is assigned.

Additional Notes:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment