### Template for DTR Memo
Project:To-do box

Group Member Names: Ashton Bailey Sara Ebbers

Project Expectations: What does each group member hope to get out of this project? A- learning jquery, and javaScript reps, have time to play with design S- good pairing experience, get to the end of project, collaborate as we build

Goals and expectations: take turns typing code, share commits, and do more frequent commits,

Team strengths: A- bring back to focus, refocusing when at a block and then coming back  S- time management, organization

How to overcome obstacles: A & S: take a moment away, and coming back.  accept there is a problem and presented-- then act to resolve.

Schedule Expectations (When are we available to work together and individually?): A- introvert, but talkative S- introvert, needs time to recharge-- A- not available Monday nights, available to work remotely or come to Turing.  S. Sat 3-10 not available, tues night softball ; A- available around 7:45 but not earlier, available after school.  S- 7:45 but not earlier, available after school.  not work during lunch if possible.  This Sunday work together Turing 10am-5pm, Th afterschool 1 hr, f 4-6 work on jq with chris, sat work individually, consider coffee shop as option.  regroup plan 30 min before leave on Sunday.

Communication Expectations (How and often will we communicate? How do we keep lines of communication open?): A- hard time reaching out when struggling with code. S- struggle too long on own.  Use slack to communicate-- text if need more immediate answer S- 828-260-0912

Abilities Expectations (Technical strengths and areas for desired improvement): both want work on JQ and JS

Workload Expectations (What features do we each want to work on?): both work on all parts.  and divy out small problems.

Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests): A set repo, regular commits, shoot for 5-10 line changes being commited.  pull up small stuff in merge but if tackling a big change talk first.

Expectations for giving and receiving feedback: if concern share early and trust it will be well recieved, assume positive intent,  talk it out.... move forward in timely way.

Agenda to discuss project launch: n/a

Ideas: n/a

Tools: pairings with mod 2  , class partner Chris

Additional Notes: be patient asking questions, and making sure there is understanding, use outside support to deepen fuzzy areas.