Skip to content

Instantly share code, notes, and snippets.

@C-Bandstra

C-Bandstra/dtr.md

Last active December 2, 2019 22:41
Show Gist options
  • Save C-Bandstra/5b60d9732c852c87db6f71b1fd6aa019 to your computer and use it in GitHub Desktop.
Save C-Bandstra/5b60d9732c852c87db6f71b1fd6aa019 to your computer and use it in GitHub Desktop.
Download ZIP
DTR: Charlie and Jeremy
Raw
dtr.md

DTR: Define the Relationship

Charlie Bandstra & Jeremy Poulter One teammate should copy and paste the raw markdown into a gist of your own.

Guiding Questions to Define The Relationship:

  • What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?

    • Start off and get a structure set up for the beginning and create or discuss our own style guide. Once we are comfortable we can branch off and work more independently but still communicate most of the time.

  • How do you communicate best? How do you appreciate receiving communication from others?

    • Being very direct, and base conversations on logic and respect.

  • How would you describe your work style?

    • Both work independently, but collaboratively. Meaning more od a driver - navigator rather than the ping-pong style. Divide and conquer is also a very efficient way to get work done.

  • What are each of our strengths? How can our strengths complement each other?

    • Want to work in the most efficient and professional way possible. Take a lot of unnecessary emotion out of the work process. Our strengths compliment eachother very well. It seems like we are on the same page about almost everything.

  • What’s gone well or poorly in your previous projects?

    • Time management was an issue for Charlie. Spacing work out, procrastinating was an issue for Jeremy

  • How will we set direction and make decisions as a team? We will establish a very detailed structure of the project. We will view eachother as equals.

  • What do you need (resources, environment, communication) to do your best work?

    • Environment is a big factor for both of us. Some of jeremy's home resources are very useful to getting tasks done. Also change work environment around the basement.

  • What scheduling restraints do you have? What are your scheduling preferences?

    • Charlie has to leave class at 4 every tuesday.

  • What is your style for giving feedback? Does anything ever hold you back from giving feedback?

    • Very cut and dry. Direct feedback is essential to efficiency in the group

  • 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?

    • Jeremy feels confident in the javascript portion and also enjoys building a visual layout before we code. His weakness is CSS and HTML styling. He can take advantage of charlie if he has any questions about clean structure. Charlie feels most confident in the HTML portion and also likes cleaning up code. He is struggling with the syntax portion of javascript. He understands the process but needs more repitition. Jeremy can help him understand any questions he has about basic javascript

  • How do you want the group to solve problems when members run into issues with features of the project?

    • Communicate in as much of an unbiased way as possible. Figure out a solution as quickly as possible

  • How do you know if a project is successful? How can we achieve that as a group?

    • review trello and rubric after every section is completed

  • How will we recognize each other's successes and celebrate them?

    • High fives and smiles boost the mood

Any additional questions that you would like to add:

Template for DTR Memo

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

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

How we can use our strengths to overcome obstacles:

What do you need to look out for, in terms of strengths/working styles coming into conflict?

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

What is the one hour/day that each teammate has on their calendar for personal study/practice time?

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

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

Expectations for giving and receiving feedback:

Additional Notes:

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