Skip to content

Instantly share code, notes, and snippets.

@kristing40
Created April 17, 2017 17:55
Show Gist options
  • Save kristing40/51ea50857d8598e29ecd0c0e730db5b9 to your computer and use it in GitHub Desktop.
Save kristing40/51ea50857d8598e29ecd0c0e730db5b9 to your computer and use it in GitHub Desktop.
Template for DTR Memo
Project: Idea Box
Group Member Names: Kristi & Karen
Project Expectations: What does each group member hope to get out of this project?
Karen: Learn how to use localstorage, write effective DTRs, understand arrays, and understand all the code in our project.
Kristi: To learn how to use local storage and persist data, understand and utilize array prototypes, effective pairing, etc.
Goals and expectations:
Understand workflow with respect to Git/Github
Learn how to be an effective developer.
Develop strong pairing skills, create bug free code, and deepen our understanding of object oriented programming.
Team strengths:
Good communication skills.
We both have skills that will work together well.
How to overcome obstacles:
Communicate about them.
Acknowledge the obstacle and then brainstorm to come to a resolution.
Schedule Expectations (When are we available to work together and individually?):
Karen: At school around 7:30am. Stay until 6pm (or later if needed).
Kristi: At school around 7:30am. Stay until 5pm (or till 5:30pm).
Work together in person before school from 7:45-9am.
Communication Expectations (How and often will we communicate? How do we keep lines of communication open?):
Revisit the DTR each evening before we leave school. Reassess where we are on the project and how to proceed.
Slack each when we create a pull request.
Try using issues on github to track when an assignment isn’t going to be completed when promised.
Resolve communication problems privately. If we can’t resolve it, escalate to mediate with either Robbie, Bree, Louisa or Ellen Mary...NOT WITH CLASSMATES
Abilities Expectations (Technical strengths and areas for desired improvement):
Gain a better understanding of OOP, using array prototypes.
Workload Expectations (What features do we each want to work on?):
TBD - all of them.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests):
Use debugger.
Work on branches in github
Pseudocode in markdown (pseudocode.md)
Expectations for giving and receiving feedback:
Kindness
Timeliness
No feedback surprises *
Agenda to discuss project launch:
Ideas: Build interface/css first and then pseudocode functionality before implementation
Tools: Jquery, Atom, chrome, dev tools, screenhero, ARIA Validator,Pomodoro timing, pairing as needed
Additional Notes:
All refactoring will be done together so that we both understand the final result.
keep distractions at a minimum
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment