Skip to content

Instantly share code, notes, and snippets.

@lundgrea

lundgrea/DTR - Tune-In-Later.md

Last active September 3, 2019 23:04
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save lundgrea/c02defe40abc3e671b483fcea90fc714 to your computer and use it in GitHub Desktop.
Save lundgrea/c02defe40abc3e671b483fcea90fc714 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
DTR - Tune-In-Later.md

DTR: Define the Relationship

Project: Tune In Later

Group Members: Aidan McKay, Chris Lane, Alyssa Lundgren

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'd like to get through at least One Extension
  • Like to be styling and finishing testing by Monday of next week
  • Want a stress-free Tuesday

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

  • Driver navigator to start and then flush out seperately as the project progresses

How we can use our strengths to overcome obstacles:

  • Communication
  • 'What's best for the team' mentality?
  • Teamwork and postitive attitude

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

  • Weekends: we will circle back around before the weekend
  • Everyone available with no specific scheduling conflicts
  • Goal: Iteration 0 today (9/3/19)

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

  • Meet in the mornings
  • Update each other if we are working seperately on what we are doing and how its going
  • Slack
  • After 10pm no merging, you can put up your pull request but don't expect it to merge until tomorrow

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

  • We want to get better at: testing, styling (simple and clean), UI, Redux, Router, React

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

  • We all want to get a chance to work on everything

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

  • Work together especially at the beginning to flush out the bones of the project
  • Take breaks
  • As we get later in the project we will discuss working more independently
  • Deal with merge conflict locally before pushing up
  • Major issues/stopping points? Let's get together.
  • Don't merge your own pull requests
  • Let everyone know ASAP for 1) pull requests or 2) merged code
  • 5-10 minute check-in before class starts
  • Include line by line code review on GitHub

Expectations for giving and receiving feedback:

  • Project-related
  • Open and honest
  • If any points of contention we will all get together
  • NO angry slack messages specifically at 2am

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

  • GitHub Projects

Day 1 Agenda:

  • DTR
  • Wireframe
  • GitHub projects
  • Setup repository
  • Submit to Travis/Robbie
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment