Skip to content

Instantly share code, notes, and snippets.

@Trond240

Trond240/project_1_timer_DTR.md

Last active October 7, 2019 20:31
Show Gist options
  • Save Trond240/0e7725f33db6ef781cdf550b2cc2dee7 to your computer and use it in GitHub Desktop.
Save Trond240/0e7725f33db6ef781cdf550b2cc2dee7 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
project_1_timer_DTR.md

DTR Memo

Project: Intention Timer

Group Member Names: Caleb Haizlett, Trond Makonese

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

  • Goal: Get through as much of the interations as we can understand.
  • Group goal: communictation is key, staying on the same page. No snow balling.
  • Sucess? Confidence that presented the best work possible.

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

  • Paired, tackling obstacles on our own but with explanations step by step when completed.

How we can use our strengths to overcome obstacles:

  • Keeping our minds and work flow fresh. Take plams every 30 minures or so. Be open to questions and feed back.

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

  • Get out of the basement by 7!!!

  • We can adjust time crunches by needs.

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

  • DTR daily with updates and progress. All opens are open until 9pm. If needed time can always be expanded. Present both ideas and agree on a common goal.

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

  • Caleb: Java Script!! CLEAN CODE

  • Trond: Java Script!! CLEAN CODE

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

  • Devide work load a up as best as poissible. Driver and navigator sistuations for when both parties need understanding.

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

  • Commincation when merging and pulling from the master branch.

Expectations for giving and receiving feedback:

  • Often and open, empathy!

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

  • GitHub project manager.

Day 1 Agenda:

  • DTR, WireFrame, Story boarding!

Additional Notes:

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