Skip to content

Instantly share code, notes, and snippets.

@KCWill
Created February 18, 2020 17:03
Show Gist options
  • Save KCWill/c5901ec1af63a79457f9dc1a040715d5 to your computer and use it in GitHub Desktop.
Save KCWill/c5901ec1af63a79457f9dc1a040715d5 to your computer and use it in GitHub Desktop.

DTR Memo

Project: Intention Timer

Group Member Names: Megan Huggins, Kyle Wong, Kyle Williams

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

  • Megan would like to understand Javascript more in general and working as a team. Kyle Woo would also like to continue working as a team and getting more comfortable with classes/objects. Kyle Wii would like to develop skills for working with a team. We will know we are successful when we complete every iteration with a group understanding of every element.

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

  • Kyle Wii's strengths include taking his time and guiding people through problems. Kyle Woo values communication in the group and is willing to listen. Megan is able to explain and step through processes to group methods. She also has perserverance that will get the job done. One possible negative that we foresee happening is getting frustrated about a difficult aspect of the project. We want communication open at all times where we collaborate on code at all times.

How we can use our strengths to overcome obstacles:

  • Kyle Wii's strength of walking through problems in a organized way will help us all tackle the problems together. Kyle Woo's strength is making sure that everyone is on the same page through open communication; keeping the big picture in mind. Megan's strengths include resilience and asking for help from more experienced coders.

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

  • Kyle Wii would prefer not to work at Turing on weekends, he is willing to set as much time as needed to work over slack. Kyle Woo will work as late as it takes at Turing, but will not work at home. Megan is fine with coming in on Weekends or working on weeknights.

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

  • We'll be working together every day during the week. The slack channel will be our main source of communication for when we're not at Turing. Majority rules if it comes to that (we don't think it will :D).

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

  • Kyle Wii would like to improve working in group skills and get comfortable with implementing classes into webpages. Kyle Woo would like to get more experience with working on classes and keeping code DRY. Megan would like to get better at array prototypes and their uses in classes.

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

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

  • We'll be working on our own branches after we update the branch with the latest version of the master. We'd like to merge into master when we are all present. We'd like to implement the Driver/Navigator system to improve the group's understanding.

Expectations for giving and receiving feedback:

  • Try not to take things personally. Address the code and not the person. If you do have feedback, provide an alternative solution rather than keep the conversation all negative. Kyle Woo appreciates being direct. We want to struggle together.

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

  • We'll be using Trello.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment