Skip to content

Instantly share code, notes, and snippets.

@larisasmiles
Last active May 11, 2017 20:59
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save larisasmiles/6791280cdc556489cf405001d04e10ad to your computer and use it in GitHub Desktop.
Save larisasmiles/6791280cdc556489cf405001d04e10ad to your computer and use it in GitHub Desktop.
DTR Night Writer w/Jim Szalewski

Guiding Questions to Define The Relationship:

  • What are your learning goals for this project? I would like to be able to feel comfortable with pairing and File.io
  • What drives us in this project? To come out as better knowing ourselves and eachother.
  • What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches? I like to ping-pong-pair. I learn better by paired programming. Divid and conquer for very small iterations....or maybe when we both have a better understanding of code.
  • How do you communicate best? How do you appreciate receiving communication from others? I am better with laying out a calendar of days/times that work for both us.
  • How would you describe your work style? I like to be organized, and I want to truly understand the compenents before jumping. When I am working, I need breaks every 30 min.
  • What are your strengths? How can our strengths complement each other? I am a organizer I am an includer I utilize my resources fully I am positive I think that our flexibility with oneanother and our down to earth nature will allow our strengths to combine easily. POWER UNITE!!!!!!
  • What’s gone well or poorly in your previous projects? I have had great experinces in all of my projects, good communication is key. I little respect goes ALONG way.
  • How will we set direction and make decisions as a team? By communication of course.
  • How will we overcome obstacles? By communication of course.
  • What do you need (resources, environment, communication) to do your best work? ALL of the above.
  • What scheduling restraints do you have? What are your scheduling preferences? I have the kiddos so anytime after 8pm on the kiddo days I can screen hero/work.
  • What is your style for giving feedback? Does anything ever hold you back from giving feedback? I am very good about complimenting and acknowledging when there is something to be said.
  • What do you identify as being your biggest strength(s) technically, as they relate to this project? Where do you feel you could use improvement in your technical skills, as they relate to this project? How can our team help support you in improving these skills? My largest strength is I am tenacious. I want to go do great. I WILL find the answer. I am a great organizer. Improvement- always improvement! I hope to be more comfortable with testing after this prject is done.
  • What tools do you want to use to manage the project? slack, mod 2 BE, git
  • How do you want the group to solve problems when members run into issues with features of the project? I want to have a sit down and regroup together, find a solution.
  • How do you know if a project is successful? How can we achieve that as a group? If we both come out with more than we came into it.
  • How will we recognize each other's successes and celebrate them? Going to lunch on thursday?!

Project: night_writer

Group Member Names:Larisa Anderson and Jim Szalewski

Project Expectations: What does each group member hope to get out of this project? To gain better experience of working with another person.

Goals and expectations: We want to go through the project, understanding the code, understanding the instructions.

Team strengths: Both very down to earth and human.

How to overcome obstacles: Regrouping....open communication.

Schedule Expectations (When are we available to work together and individually?): checked and done.

Communication Expectations (How and often will we communicate? How do we keep lines of communication open?): everyday, tele..

Abilities Expectations (Technical strengths and areas for desired improvement):TDD, and git

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

Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests): git

Expectations for giving and receiving feedback: must be nice.

Agenda to discuss project launch:

Ideas:

Tools:

Additional Notes:

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