GlobeTrotter DTR

GlobeTrotterDTR.md

Group Member Names:

• Colin Koga, Zac Isaacson, John Travers, Scott Ertmer, Austen Dunn

Goals and Expectations for the Project (You don't know the details of the project yet. But as you go into any project, how do YOU define success?)

• Colin Koga: learning new lang (native) and solid testing, and D3.
• Zac Isaacson: Learning django/ flask is a priority. New lang's and frameworks.
• John Travers: Getting more comforatble with python, new frameworks and langs
• Scott Ertmer: React native, working with D3 for some visual magick
• Austen Dunn:

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

• Colin Koga: Strong inital planning
• Zac Isaacson: Strong base understanding of what we are doing, then breaking it out into stories
• John Travers: stengths: SQL, postgres, testing. Collaboration: strong planning, and then divide and conquer.
• Scott Ertmer: Strong initial planning, organization and userstories written.
• Austen Dunn:

How we can use our strengths to overcome obstacles:

• Colin Koga: communication
• Zac Isaacson: Open communication, transparency helps.
• John Travers: Ditto!
• Scott Ertmer: open and direct communication
• Austen Dunn:

Schedule Expectations (When are we available to work together and individually? What constraints do we have?):

• Colin Koga: Health issues means working from home is preferable
• Zac Isaacson: Don't feel bad about taking and making time for job search requirements, just be transparent
• John Travers: flexible - night person
• Scott Ertmer: flexible - no other comitments, moving apartments this weekend.
• Austen Dunn:

Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):

• Be open, be direct, be kind. Daily standups. slack any time, but don't expect a response after 9 pm.

Workload Expectations (How are we going to make sure we contribute equally?):

• pull your weight.

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

• Colin Koga:
• Zac Isaacson: template for pull requests. At least 2 other's must review your code before they merge it in. Document along the way.
• John Travers: Never push to master, checklist for user stories. test coverage documented in the PR template. under 40 char
• Scott Ertmer: comments and questions on code reviews. atomic commit
• Austen Dunn:

Expectations for giving and receiving feedback:

• kind, actionable, specific, direct, early.

Project management tools we will use (GitHub Projects and Trello are popular tools):

• GH projects.

Other Notes:

• Scott's migraines - will do everything I can to prevent them, and will communicate as soon as I know. Might miss a day or two, but not super likely.