Skip to content

Instantly share code, notes, and snippets.

@ericweissman
Last active April 2, 2019 00:41
Show Gist options
  • Save ericweissman/68d896ab9ef78087396a65a903c88f9f to your computer and use it in GitHub Desktop.
Save ericweissman/68d896ab9ef78087396a65a903c88f9f to your computer and use it in GitHub Desktop.
Cross Pollination DTR - Eric Weissman, Nick Lindeberg, Lance Taylor

Project: Habit Golf

Group Member Names: Eric Weissman, Nick Lindeberg, Lance Taylor

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

E: Solidy FE concepts by creating a intuitive and simple UI for our FE. Want to get experience working with BE engineers and using a rebase workflow. Eager to work on incorporating a new technology, hopefully React Native or PWA for a mobile experience. As a team, I would like us to arrive at a MVP we are proud of and can speak intelligently about. N: To work with a new cool, new technology on the BE (TBD on what that is going to look like). L: Interested in exploring different database structures.

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

E: I feel comfortable with open communication and project management to make sure we are on track for deliverables and communicating if there are any blockers, etc. N: Feels confident with building APIs. L: Prefer to rubber duck with someone when stuck. Prefer working individually.

How we can use our strengths to overcome obstacles:

E: Communication is going to be the biggest challenge but also most imperative for our success. Pairing if blocked. N: Keep an even keel and pair on FE when available. L: Keep to an agile model - setup user stories for MVP. Prioritize pieces of functionality and work through them and document progress.

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

L: Prefers to work solo in mornings, usually try to leave Turing by around 5:30 latest. N: Get in around 8-8:30 and usually stick around till 6-6:30. Wednesday nights try to get off on the earlier side. E: I will likely be here after school and on the weekends to take advantage of other FE people in the building.

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

L: Ideally do a checkin all together at least once a day, either as a standup or in-person. Communicate timelines on deliverables. N: Slack and in-person. E: Slack and slack-calls/standups for when we are remote just to checkin.

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

L: Trying to avoid rabbit holes and recognize when it may be better to pair/get a second set of eyes. I feel strong with API design and querying datanbases. N: Environmental factors, such as CI, are areas I want to continue to work on. Also feel strong with API design and querying databases. E: I want to get better at testing and working to integrate a new technology. I feel solid with React fundamentals and setting up Redux.

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

L: Focus on building backend. N: BE and will help with FE if/when needed. E: Focus on creating FE.

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

All: Want to work on rebase workflow.

Expectations for giving and receiving feedback:

E: Be straightforward but also cognizant of where everyone is at mentally. L: Make sure you are being kind and honest in feedback. N: Be kind - everyone is trying to learn, everyone is at different levels and everyone feels like we are really far apart in school.

Project management tools we will use:

We will use waffle.io for it's last hurrah.

Day 1 Agenda:

  • Work through DTR
  • Create rough schema
  • Create initial user stories
  • Create initial wireframe
  • Work on scope of MVP

Additional Notes:

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