Skip to content

Instantly share code, notes, and snippets.

@ameseee

ameseee/ah-2dobox.md

Last active July 30, 2017 03:21
Show Gist options
  • Save ameseee/d0495ea53021c00504f5d9178fd412a4 to your computer and use it in GitHub Desktop.
Save ameseee/d0495ea53021c00504f5d9178fd412a4 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
ah-2dobox.md

DTR Memo

Project:

2DoBox-Pivot

Group Member Names:

Amy, Erik, Sam

Project Expectations: What does each group member hope to get out of this project?

  • Erik: more practice of JS functionality, GitHub workflow
  • Sam: implement JS code with more fluency
  • Amy: improve refactoring skills & GitHUb workflow

Goals and expectations:

  • Complete the project.
  • Follow through on what you say you'll do - or communicate proactively if you can't!

Team strengths:

  • We all bring positive energy & excitement to both learn and work together.
  • Erik and Amy have already worked together and established a great working relationship.
  • Sam is strong in explaining JS concepts clearly

How to overcome obstacles:

  • Work as a team, no blame game
  • Ask questions
  • Only bang head against the wall for 30 minutes - use resources wisely

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

  • Erik and Sodie & Oscar have haircuts on Saturday morning. Other than that, we are all in.
  • Kick off together work-time Saturday around noon at Prodigy Coffee SHop.
  • Work together on Sunday at Turing.
  • Monday night is out.
  • 8:45am check-ins Monday-Thursday.
  • Use pairings for project goals, once we chunk out and assign functionality pieces to each team member.

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

  • Several times daily in person
  • Waffle
  • Slack
  • Text
  • ask if the other person 'has a minute'

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

  • Amy is organized, and kind of gets JS but need to improve to completely understand the code.
  • Erik gets things logically, but struggles to write the code.
  • Sam is strong in HTML and CSS, wants to improve in implementing JS.

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

  • We will circle back to this after initial meeting.

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

  • Waffle - assign each task with name
  • Push to github on each small chunk of progress

Expectations for giving and receiving feedback:

  • quickly, as soon as a concern comes up.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment