Skip to content

Instantly share code, notes, and snippets.

@attom2
Created June 29, 2020 23:00
Show Gist options
  • Save attom2/b45e0205480791eaeb84cd6db162706e to your computer and use it in GitHub Desktop.
Save attom2/b45e0205480791eaeb84cd6db162706e to your computer and use it in GitHub Desktop.

Group Member Names: Andy Tom and Becca Steinbrecher

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

Andy: I haven't built an app in react so I'd like to just have practice with that. Know more about react. Becca: Understand the router that creates multiple pages for the user experience. Asynchrous testing with jest. Both: If we learned what we want to learn. Hopefully be done with iteration 5 by next wednesday.

Team strengths & collaboration styles (consider discussing your Pairin qualities here):

Andy: Likes to work step-by-step toward a goal. Becca: Straigtforward and sincere, optimistic. Both: Specialist, work hard and plan.

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

Both: Take a break at 4. Don't work after 7:30. No working on friday night. If possible, try to take most of a day off.

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

Andy: Mostly verbal, don't like too much over text. Becca: Okay with texting communication, try to include an emoji and reassurance the partner is up to speed. Be mindful of each others state of being. Agile for shifting priorities. Make decisions together on a call.

Abilities & Growth Expectations (Technical strengths and areas for desired improvement):

Both: More react practice.

Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):

Trello, if we're mostly pairing we won't have to review as much or pull request issues. If we write code separately, look over each others.

Pomodoro Break Schedule:

30 mins on, 7 mins off. After 2 or so hours, take a longer break.

Expectations for giving and receiving feedback:

Both: Be straightforward and sincere.

Additional Remote Considerations:

Maybe we could meet in person.

Project management tools we will use (GitHub projects or Trello are popular tools):

Trello

Day 1 Agenda:

Finish wireframe, DTR, PR template, start Trello

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment