Insert app idea here This document describes our team social contract for this project Reference Establishing Norms
- Taskmaster
- Gitmaster
- Testmaster
- Morning standup started by yesterday's Taskmaster
- New roles assigned (by yesterday’s Taskmaster)
- Yesterday? Today? Obstacles? (by today’s Taskmaster)
- Pair program on assigned tasks
- Bring up any blocking issues after after solutions are exhausted of spinning your wheels
- At 2:30pm have re-group meeting where you check-in with blockers, status updates and plan for EOD merge
- Immediately prior to end of day make applicable PRs, review each other’s code and merge into master
- If Block is Error related REACH OUT IMMEDIATELY. If it is minor related push issue into GitHub or when we next meet.
- 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 you have a blocking issue, slack before interrupting another’s train of coding-thought
- We will assign tasks vertically (instead of horizontally) None of us will specialize in terms of front-end and back-end code
- Don’t interrupt
- Share the mic
- Disagree often and discuss -- argue infrequently
- At least message the group when you change what you are working on
- If the group is divided on a certain decision we will take the following steps:
- Take 10-15 minute break
- List out the pros / cons
- Vote on it
- If the vote is split, escalate to a fellow or instructor
- If you are frustrated
- Take a walk or get some water
- Talk constructively about actionable items (e.g. raise your hand instead of interrupting, let me learn and struggle until I ask you for help, etc.)
- Bring in a 3rd party (e.g. fellow, instructor) to mediate if you feel too frustrate