Skip to content

Instantly share code, notes, and snippets.

@spaceplesiosaur
Created August 19, 2019 21:44
Show Gist options
  • Save spaceplesiosaur/18b7cc173d24775f39709921fd18baf6 to your computer and use it in GitHub Desktop.
Save spaceplesiosaur/18b7cc173d24775f39709921fd18baf6 to your computer and use it in GitHub Desktop.

Template for DTR Memo

Group Member Names: John, Allie

What feedback did you get on Dog Party today? What was your biggest takeaway?

Allie: Clean up your code! And don't go to a new iteration until you're done with the first.

John: Don't overdue media queries

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: Get through all the iterations, and get them to work

Allie: Complete all iterations as much as possible, bonus is completing all. Better have 3 at 100% than 5 at 80%.

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

Allie: Night owl, ambivert, self-examiner, transcendance John: Flexible, introvert, conflict-wrangler, moderation

How we can use our strengths to overcome obstacles:

Allie: Can usually stay positive, and catch myself if I get into a "I suck!!" spiral

John: Task driven and flexible, level headed, doesn't get stressed easily

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

Allie: Coming from Boulder, night owl 8:22pm - 12:30pm, ballet on Wednesday

John: flexible night/morning hours, Golden (light rail, every 15 minutes during rush hour, 35 minute ride), works to 11:30?

8:30 am - stand ups every day

Retros after each phase (Th, Monday)

Tuesday and Thursday stay late - 9 at the latest

Weekends - check in Friday, Allie's pretty open (ballet 1-3), John's pretty open, meet b/t Golden and Boulder

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

Standups: T/TH/F Retro: Friday, 30 minutes before leaving If we're stuck, reach out to other person. Send code snippits Allie get slack on phone! Ping each other if late for standup

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

Allie: CSS blocking, neatness (areas of improvement) JS (comfortable)

John: CSS (comfortable), JS (comfortable)

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

Keep track of commits and do as much work as possible together, check how many commits each person did during standup.

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

Git workflow - tell each other before we do a push, push during standup, if we're working together push together (neither of us have done git workflow in pairs, we expect to adjust as we go) Tools - Slack, Google cal, Try trello if it's getting hard to keep up on tasks (if either one of us has having trouble)

Review each other's code after push before it's added to the repo, touch on during Standup.

Expectations for giving and receiving feedback:

Honesty, be nice, stay positive

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

Check GitHub and Trello for 10 minutes tonight to see which is better.

@allisonreusinger
Copy link

I appreciate how you really emphasized your strengths and preferences here as well as a set schedule for how you can work together. Nice job!

@spaceplesiosaur
Copy link
Author

spaceplesiosaur commented Aug 20, 2019 via email

@allisonreusinger
Copy link

allisonreusinger commented Aug 20, 2019 via email

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