**Project:**

**Group Member Names:** Michael Marlow and Francy Lang

**Project Expectations: What does each group member hope to get out of this project?**
* *Learning goals of the project.*
* *Feel good about the work we complete and be able to speak to our code.*

**Goals and expectations:**
* *Save extensions for the end.*
* *Be successful- pairing, execution of the project.*

**Team strengths:**
* *Francy: Organization, staying calm.*
* *Mike: Problem-solving.*

**How to overcome obstacles:**
* *Pairings setup for next week.*
* *Make sure both partners understand the changes and the code.*
* *Communication, no suffering and stressing in silence.*

**Schedule Expectations (When are we available to work together and individually?):**
* *Saturday: 10AM*
* *Sunday: afternoon*
* *Next week, open availability.*

**Communication Expectations (How and often will we communicate? How do we keep lines of communication open?):**
* *Morning check-ins*
* *Pause, when someone needs more time to process*
* *Evening check-ins*

**Abilities Expectations (Technical strengths and areas for desired improvement):**
* *Desired improvement: conditional logic.*
* *Strengths: html, css, problem solving, psuedo coding.*

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

**Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests):**
* *Coding together, use waffle.io, communicating pushes to github.*

**Expectations for giving and receiving feedback:**
* *Thoughtful (not impulsive) feedback.*

**Agenda to discuss project launch:**
* *

**Ideas:**

**Tools:**

**Additional Notes:**