Skip to content

Instantly share code, notes, and snippets.

@QuinnrElder
Last active May 26, 2020 17:37
Show Gist options
  • Save QuinnrElder/6ff00abe02add3bb013f0ad38836b1df to your computer and use it in GitHub Desktop.
Save QuinnrElder/6ff00abe02add3bb013f0ad38836b1df to your computer and use it in GitHub Desktop.

DTR

Project: stretchGroup -

Group Member Names:

John Watterson Michelle Kaplan Rachael Thomas Quinn Elder

Project Expectations:

  • We want to accomplish an MVP of at least iterations 0 - 4
  • John Watterson implements unique API within React, a better grasp of TDD, manipulate state with HOOKS.
  • Michelle Kaplan implements unique API within React, Testing within these unique API, HOOK // STATE.
  • Rachael Thomas how and why using HOOKS, HOOKS management implementation, get personal reps in with new technologies.
  • Quinn Elder SAME^

Team strengths:

  • John Watterson great within group dynamics
  • Michelle Kaplan spelling and grammar :) Fundamentally sound in React, Colab // Communication
  • Rachael Thomas WorkFlow, Project management, Organization, Communication
  • Quinn Elder easy going, willing to sacrifice time for others and projects MVP.

How to overcome obstacles:

  • Reach out for help early and often (if the teammates can't find the answer)
  • Utilize mentors if and when possible. Try to involve the group in the mentor meetups if the project is involved.

Schedule Expectations (When are we available to work together and individually?):

  • We have a bunch of scheduled work time on the calendar — so we will utilize that

POM MOTHER F'ERS 40:7 Friday Night: after retro we are done!

----WEEKDAYS---- MORNINGS: are for pairing till noon"12pm'' LUNCH -2pm: personal research and fact-finding 2pm-5:30pm: More pairing After Dinner: PD, Study time, Research, Pairing if needed

----WEEKEND----

  • start pairing at 10am
  • try to wrap up around 5pm

Communication Expectations (How and often will we communicate? How do we keep lines of communication open?):

  • Just reach out. The group is open to communicating on Slack via messages and then a follow-up call.
  • Be forthright with one another. If there is a change in schedule, simply tell your group.

Workload Expectations (What features do we each want to work on?):

  • Ensuring that everyone gets a chance to Drive vs navigate.
  • Each group member needs to have at least 1 PR within each technology
  • When pairing and Megeing ensure that if it was work done while pairing all members involved are mentioned in the PR

Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests):

  • Since REACT is rather new to both parties, we will be working in tandem in a driver-navigator scenario.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment