Team Norms

Each of us reserves the rights to our nights and weekends, and we have all been straightforward about when and how we can commit to working on the project
If a group member plans on working off hours, or feels inspired, they'll send a quick heads up so everyone is on the same page
We expect that no one will merge the main branch until we have had a code review, or we have discussed the newly added functionality (this will happen once a day)
Anytime we get frustrated, be it our own code or during a discussion in a tense decision making stage, we take a 5 min breather then regroup
Come to stand-up with root cause of any issues or bugs we've run into, with a quick what happened, where, why and how to avoid going forward
If you're taking a break during working hours, you send a message to the slack channel to let us know you'll be unavailable
We'll keep the paired programming sessions fluid and open to personal interpretation. People switch when they feel like they've reached a good stopping point

Steps to reach an agreement:

Everyone says their piece about what direction they believe we should go, we have a conversation to start to see if we can get on the same page
If no agreement can be reached, or we're at a stalemate, then it goes up to a vote. We explain why we voted that way and why we feel strongly about it so hopefully no one feels hurt or left out of the decision
If residual feelings or thoughts exist and we still can't reach an agreement, we'll escalate to our mentor/instructor

Tuesday (the 15th)

Thinking about & discussing ideas and consultation with Mentors & Instructors (Proof of Concept Ideation)
Social Contract Definition
Team Norms Definition
Github Organization Creation

Thursday (the 17th)

Friday (the 18th)

Monday-Tuesday (21st-22nd)

Provide feedback