Skip to content

Instantly share code, notes, and snippets.

@dawnlunacy
Last active August 20, 2019 02:22
Show Gist options
  • Save dawnlunacy/edfcc77eb08e2af83dce12d6b36312c1 to your computer and use it in GitHub Desktop.
Save dawnlunacy/edfcc77eb08e2af83dce12d6b36312c1 to your computer and use it in GitHub Desktop.
This is the DTR between Lacy and for FitLit : the first paired project of Mod 2 at Turing School for Software and Design
DTR: Define the Relationship
Project:FitLit
Group Member Names: <br>
Lacy Rudd & Foster Taylor
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?): <br>
Lacy: I would like to get through the entire project, with an interactive interface for the user. If at all possible would love to maybe have a drop down list with the names for admin view extension, ensuring our commits are equal.
I would also like to do the entire project writing Tests first, and implementing the DOM as we go.
Refactor with ternaries*
Foster: *Learn* as much as possible, with awesome collaboration and communication. Navigating, driving, switching.
Team strengths & collaboration styles (consider discussing your Pairin qualities here): <br>
Lacy: Patient and committed to learning at our own pace, happy to help and explain things.
Foster: Good at teamwork, fairly neutral in general.
How we can use our strengths to overcome obstacles: <br>
Schedule Expectations (When are we available to work together and individually? What constraints do we have?): <br>
** 30 min to an hour of codewars/ iron Fe/ JsFun at the begginning **
*** Lacy: I would like to leave 6:30 every day. In person Saturday - 9am - 2pm Saturday. Try to work remote on Sunday.
Foster: Needs to leave by 2pm this Saturday -- Aug 24th. Otherwise okay with the above.
Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?): <br>
Lacy: Open, honest, often.
Foster: Communicate often, having a plan for the next day at the end of the day. Using slack.
Abilities & Growth Expectations (Technical strengths and areas for desired improvement): <br>
Lacy: getting faster using prototypes.
Foster: Goal of TDD and understanding how to use it. Lay foundations for future projects.
Workload Expectations (What features do we each want to work on?): <br>
Lacy: I would like to challenging myself to do more html and css. Also overall divide by iterations. Do iteration one together and then divide up the rest.
Foster: Would like to focus on JavaScript, more so than html and css, but in general even contributions.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques): <br>
Lacy: Challenge to use the github project board. Each other merge each others code. Try to minimize co-authors and really focus on switching driver and navigator.
Foster: Have used trello in past, open to change it up.
Expectations for giving and receiving feedback: <br>
Lacy: Address problems as soon as they come up
Foster: Open honest
Project management tools we will use (GitHub projects or Trello are popular tools): <br>
Github projects
Day 1 Agenda: complete DTR, set up files for UserRepo tests and class, and User tests and class, familiarize Foster with jsFun.
Additional Notes: Both of us are excited to learn as much as we can from this project.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment