Skip to content

Instantly share code, notes, and snippets.

@hljacobs5

hljacobs5/Game Time DTR.md

Created May 1, 2018 21:11
Show Gist options
  • Save hljacobs5/443eeb5480fdb426cefdb44b50feb2ce to your computer and use it in GitHub Desktop.
Save hljacobs5/443eeb5480fdb426cefdb44b50feb2ce to your computer and use it in GitHub Desktop.
Download ZIP
Raw
Game Time DTR.md

Template for DTR Memo

Project: GameTime

Group Member Names: Haley Jacobs, Jesse McFadden

Project Expectations: What does each group member hope to get out of this project?

A better understanding of object oriented programming, code organization, javascript and canvas.

Goals and expectations:

To complete the project on time and achieve a score of 3 or above in all categories of the rubric.

Team strengths:

We both thrive in relationship building and strategic thinking.

How to overcome obstacles:

We can use our relationships with alumni and mentors as well as other classmates to work together to overcome obstacles.

Schedule Expectations (When are we available to work together and individually?):

We are both available all of the time. Unless progress isn’t being made together we will plan on working together for the majority of the project.

Communication Expectations (How and often will we communicate? How do we keep lines of communication open?):

We will communicate in person, via slack or text message. We will be sure to communicate with each other directly if there are any issues that come up.

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

Haley: Would like to get better with object oriented programing, arrays, and methods.

Jesse: Would like to get a better understanding of OOP, array prototypes and javascript.

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

We would like to have the project successfully hosted on Github.

Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests):

Unless there is an issue with using it, we will use a checklist like apple Notes to keep track of our progress.

Make sure we both go over code in-depth prior to evaluation.

Expectations for giving and receiving feedback:

We’re both open to direct feedback in the moment.

Agenda to discuss project launch:

  1. Process: We would both like to start with proper planning to develop an understanding of

Ideas:

Tools:

Additional Notes:

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