Skip to content

Instantly share code, notes, and snippets.

@Leasw144
Last active August 17, 2020 23:00
Show Gist options
  • Save Leasw144/60d3f322c68ff41e684a5f45d2edf21b to your computer and use it in GitHub Desktop.
Save Leasw144/60d3f322c68ff41e684a5f45d2edf21b to your computer and use it in GitHub Desktop.
DTR For Mod 3 Rancid Tomatillos

Project: Rancid Tomatatillos

Group Member Names: Naomi Ware, Horacio Borrego, Linus Leas

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?): We would like to achieve a base level of understanding of how React works. Naomi would like to have more familiarity using the API in terms of fetch requests, as would Linus and Horacio. Success is determined in how we each understand and can describe eachother's code and if we can get to iteration 3/reach full functional

Team strengths & collaboration styles (consider discussing your Pairin qualities here): Horacio is agreeable in terms of work styles, and has a good understanding of CSS and responsiveness in app design. Naomi prefers paired/group work and likes to discuss through concepts before implementation, and is strong in debugging. Linus is also strong in debugging and is good at seeing control flow. His preference is also in group/paired work.

How we can use our strengths to overcome obstacles: Naomi has strong communication skills in terms of talking through problems, and also being open to other avenues to find solutions. Horacio similarly feels the same way in terms of getting everyone's opinions and determining the best course of action. He is also well versed in using tools for debuggers. Linus also likes to work in groups when it comes to debugging and using his knowledge of control flow and chunking big problems into smaller parts.

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):

The group has decided on a hard stop at 9pm with open communication if there are any scheduling conflicts that may arise. Work time given during school hours should be used to its fullest extent. At minimum, we plan at least 4 hours each day including school hours. Generally looking at 2-4pm during school hours when given, and start again at about 5:30.

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?): slack.

Abilities & Growth Expectations (Technical strengths and areas for desired improvement): Linus and Naomi would like to get more familiar with fetch requests, Horacio would like to be familiar with React workflow

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

Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques): Everyone should make thoughtful comments on PRs that will be merged. In terms of group work, it would be helpful to make a note on who was participating/collaborating on that particular PR

Pomodoro Break Schedule: 50 on, 10 off

Expectations for giving and receiving feedback: We expect open and honest communication early and acknowledge that all parties are open to constructive criticism. Feedback should be about the work and not the person.

Additional Remote Considerations:

Project management tools we will use (GitHub projects or Trello are popular tools): GH Projects Day 1 Agenda: Provide deliverables:

  • DTR
  • Wireframe
  • Create group with instructors
  • Send Link of Project Board Additional Notes:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment