Skip to content

Instantly share code, notes, and snippets.

@attom2
Created July 20, 2020 17:43
Show Gist options
  • Save attom2/edc1463521da43e3a15477bf514f183d to your computer and use it in GitHub Desktop.
Save attom2/edc1463521da43e3a15477bf514f183d to your computer and use it in GitHub Desktop.
Strech-Project-Name-That-Pokemon.DTR
Group Member Names: Andy Tom, Corbin March, Edwin Montealvo
## 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?):
Corbin: Have a firm grasp on React Hooks.
Andy: Have a better understanding of React fundamentals.
Edwin: Start to understand Typescript.
## Team strengths & collaboration styles (consider discussing your Pairin qualities here):
Andy: Everyone willing to work, Lover of Justice.
Corbin: Fully detailed workboard to work through.
Edwin: Willing to help others along if they are willing to work.
## Schedule Expectations (When are we available to work together and individually? What constraints do we have? Make sure to discuss the remote questions above in regards to this section):
Don't schedule calls for 6pm or later, still continue working.
## Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team? How will we communicate about our emotional and mental well-being with each other?):
Mostly verbal, don't like too much over text.
Be mindful of each others state of being. Agile for shifting priorities. Make decisions together on a call.
No slurs or violence.
## Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
More react practice, solid understanding of useReducer and useEffect. Try out creating own custom hooks. Good, small commits and use of PR template.
## Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
Github projects
Small commits, use PR template, Code Reviews if we aren't pairing.
## Pomodoro Break Schedule:
30 mins on, 7 mins off. After 2 or so hours, take a longer break.
## Expectations for giving and receiving feedback:
Be straightforward and sincere. Non-violent, actionable feedback. Best to give verbal feedback, maybe along with text feedback.
## Additional Remote Considerations:
Maybe we could meet in person.
## Project management tools we will use (GitHub projects or Trello are popular tools):
GitHub Projects
## Day 1 Agenda:
Finish wireframe, DTR, PR template, start GitHub pages, Create an MVP to send to teachers.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment