DTR Memo Project: Refactor Tractor
Group Member Names: Allie, Colin, Matt
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?): Knowing all of the key concepts, understanding each other's code enough to talk about it and rewrite it.
Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
Colin: prefer not to work this weekend. Not responsive after 8
Matt: No weekends if possible, gone the weekend after next. Not responsive after 10.
Allie: Can't stay late Wednesday, has a sick cat, half capacity for first weekend. Not responsevise after midnight.
Alex: Very flexible, prefer not to meet in the morning
Standup Monday, Wednesday, Friday at 4.
Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
Always slack before making PR Git review Templates
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
PR reviews - no merging unless we review. Pair on trounble spots. Leverage mentors.
Expectations for giving and receiving feedback:
We all prefer hard feedback as long as it's not cruel and personal, should be constructive. Not us against each other, it's us against the project
Template for DTR Memo Project:
Group Member Names: Allie and Alex
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?): Knowing all of the key concepts, understanding each other's code. Get through iteration 4 at the least.
Team strengths & collaboration styles (consider discussing your Pairin qualities here):
Alex: Talking through problems, communication
Allie: Breaking down functionality into smaller pieces and estimating how long each will take for delegation purposes, usually pretty easy going, will not take out nerves on partner.
How we can use our strengths to overcome obstacles:
If we recognize we're in a trouble spot, we'll know to talk through it to get through it
Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
Allie: Can't stay late Wednesday, has a sick cat
Alex: Very flexible, prefer not to meet in the morning
Stay late Tuesday, Thursday, Friday, no obligation to stay after 7. Try not to stay late on weekends!
Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
Pair slack, merge each other's PR's. Stand-up every day and merge - 1st 10 minutes of lunch, and before we leave
Retros after each iteration, if anything big comes up
Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
Allie skills and areas of improvement - Need more confidence in what I know vs what I don't know (need to improve), want to be more comfortable with array prototyoe functions
Alex skills and areas of improvement - Need more confidence in what I know vs what I don't know, want to get very comfortable with media queries
Workload Expectations (What features do we each want to work on?):
Need to look at rubric. Try to make it as even a split as possible
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
PR reviews - no merging unless we review. Pair on trounble spots. Leverage mentors.
Expectations for giving and receiving feedback:
We all prefer hard feedback as long as it's not cruel and personal, should be constructive. Not us against each other, it's us against the project
Project management tools we will use (GitHub projects or Trello are popular tools): Personal organizers
Day 1 Agenda: