Created
October 8, 2019 16:58
-
-
Save MillsProvosty/70260e7d73b56476265a89258b30599c to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
DTR: Define the Relationship | |
Project: Calorie Counter | |
Group Member Names: | |
Mills Provosty, Jake Miller | |
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?): | |
- Jake: We will both be gainfully employed by the time the project is done. | |
- Mills: I will be comfortable making API calls in Javascript | |
Team strengths & collaboration styles (consider discussing your Pairin qualities here): | |
- Mills: Planning, organization, communication | |
- Jake: Coding all the things. | |
Schedule Expectations (When are we available to work together and individually? What constraints do we have?): | |
- Mills: Like = out by 7:15pm latest, Non negotiable =Sunday 9:30-1 pm piano lessons, otherwise, time is 100% open. | |
- Jake: Like = out by 7pm, | |
General: Please slack | |
Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?): | |
-Slack when something changes project | |
-Daily Retro at 8:30/Check-ins: Progress, hold-ups, goals for the day, poms, work time expectations. | |
Abilities & Growth Expectations (Technical strengths and areas for desired improvement): | |
-Jake: JavaScript conventions, styling | |
-Mills: API calls, conventions | |
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques): | |
Don't merge your own code, commit pattern: test/functionality = a pushed commit. | |
Have template for PR's, super descriptive. | |
All functionality, including model instance/class methods should be tested and passing before push. | |
Expectations for giving and receiving feedback: | |
Kind, specific, actionable and timely. | |
Be direct. | |
Project management tools we will use: | |
Github | |
Projects board | |
Slack | |
Day 1 Agenda: | |
Set up Repo | |
Create Project Board | |
Come up with plan of attack! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment