Skip to content

Instantly share code, notes, and snippets.

@spaceplesiosaur
Last active February 14, 2020 21:51
Show Gist options
  • Save spaceplesiosaur/703e20d26970381f058f006482f814f0 to your computer and use it in GitHub Desktop.
Save spaceplesiosaur/703e20d26970381f058f006482f814f0 to your computer and use it in GitHub Desktop.

DTR Memo

Ballroom Beats

Group Member Names:

Allie, Consuelo, Allison, John

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

Allie: Make a project from start to finish, make something presentable, get more familiar with testing, learn a new language, nail down the git workflow Consuelo: Learning React Native, testing, working app by the end, keeping a good group dynamic John: Build a functional backend in Go Allison: Excel in mobile app front end design, hone in on front end processes, great working app

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

Allie: Project managing, breaking stuff down into chunks and assigning it, testing Consuelo: Good communicator, once started on something like to get it done, good commits. Allison: Frontloading and planning, wireframing and doing a schema design, pseudo coding, staying level-headed John: Planning ahead, working through problems, figuring out new tech

How we can use our strengths to overcome obstacles:

Backend teachers know Go, friends who have done React native Plan ahead, find out what kind of help we'll need before we need it Use our resources Allison is good at remaining positive, she can be our cheerleader, remain postive

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

Allie: Night owl Allison; Early bed Consuelo: Posse meetings 10:30 bedtime. John: Not able to work after 8

Check in and get each other's schedules 3 days ahead of time if you're going to be working with that person

Communication Expectations

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

StandUp every day at noon Project board - GitHub Projects Slack - merge each other's PR's

Abilities & Growth Expectations

(Technical strengths and areas for desired improvement):

Allie: Learn a new language Consuelo: Learn a new framework Allison: Learn a new framework, solidfy a process John: Learn Go

All: learn mobile!

Workload Expectations

Equal work, everyone put in as much as possible

Workflow Expectations

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

Git project board

Expectations for giving and receiving feedback:

Allie: Hard feedback ok, just not mean or personal Consuelo: Honesty, let her know if she's not being a good partner John: Values feedback, tries to be a better person Allison: You get to learn from another person

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

GitHub Projects Issues

MVP

  • The user can choose which song they want to play

  • The app will render songs from Spotify with a time signature that fits the dance

  • The user can hit start when they are ready to dance, and will see a countdown

  • The user's finger taps will be registered and recorded by the app

  • The app will only register taps on the beats, in the right spot

  • The app will record number of correct taps and compare it with the number of expected taps for a song.

  • The app can play a single song (we're choosing Beyond the Sea)

  • The app can render animated footsteps that sync with the beats of the song

Day 1 Agenda:

  • DTR
  • Initialize Repos
  • Set up scrum board
  • Normalize workflow with PR Template
  • Determine MVP
  • Create Wireframe
  • Contruct schema design
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment