Skip to content

Instantly share code, notes, and snippets.

@sertmer

sertmer/Fit-Lit-DTR.md

Last active October 7, 2019 23:21
Show Gist options
  • Save sertmer/c89d13b5c14fd90e1276441a875697d5 to your computer and use it in GitHub Desktop.
Save sertmer/c89d13b5c14fd90e1276441a875697d5 to your computer and use it in GitHub Desktop.
Download ZIP
Fit Lit DTR - John Adams and Scott Ertmer
Raw
Fit-Lit-DTR.md

Template for DTR Memo

Group Member Names:

  • John Adams and Scott Ertmer

Goals and Expectations for the Project (You don't know the details of the project yet. But as you go into any project, how do YOU define success?)

  • John: coming out the project feeling good about it, specifically understanding and applying the learning goals.
  • Scott: ditto - big focus on growth over previous projects.

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

  • John: Communication - being reliable, honoring commitments. Prefers time to process and consider everything.
  • Scott: Communication, re: conflict or difference in approach. Visual design, and recognizing patterns. Also prefers time to process.
  • Both: prefer working in person.

How we can use our strengths to overcome obstacles:

  • John: Constant Communication - staying on the same page.
  • Scott: Ripping the band-aid off when it comes to dealing with issues - quickly, directly, and kindly.

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

  • John: Here before 8, very open in evenings.
  • Scott: Ditto.
  • Both: Mostly going to work during the evenings, 8:30 AM check in's.

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

  • 8:30 AM check in's. Slack first, text second if emergency, but don't necessarily expect a response after 9pm. In person prefered. Retro on friday (lunch for now) to make plan for weekend, re-DTR, etc. Trello for delegating tasks. Constant communication will lead to collaborative decision making. Focus on Driver/Navigator or in-person paired.

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

  • John: Grow: Testing, being fluid when wondering which method to reach for. Glow: Planning code. CSS. Prototype methods
  • Scott: Grow: Testing, prototype methods, pseudo - planning the steps before coding. Glow: CSS, Visual planning.

Workload Expectations (How are we going to make sure we contribute equally?):

  • Working in person mostly, drive/nav or just side-by-side. Contributing equally means giving it your personal best, even if that is different per person.

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

  • Trello, debugger, verbose PR's, not merging your own pull req's. Atomic commits. Cleaning out logs and pseudo before merge to master. Starting workflow means pull down from master, and immediate jumping to a branch. Code reviews during morning stand up.

Expectations for giving and receiving feedback: Deliver feedback honestly and kindly. Feedback welcomed, and encouraged - it helps us grow.

Project management tools we will use (GitHub Projects and Trello are popular tools):

  • Trello.

Other Notes:

  • Scott's migraines - will do everything I can to prevent them, and will communicate as soon as I know. Might miss a day or two, but that is less likely.
  • Warm up on JSfun, IronFE, or codeWars. Half hour minimum for now - 4:30 - 5:00.
  • weekends: Very open to coming in all day, remotely, or both. One day full time, one day half day.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment