Skip to content
Milo Anderson edited this page Mar 15, 2019 · 5 revisions

Communication Plan

Since we will all be on campus, we will communicate in person. If a member can not make it to campus, we can always use slack. We think in our group, there are no issues with being heard. In our planning process, everyone got a chance to express their ideas. We take the time and really listen to each other.

Conflict Plan

Conflict doesn't seem like it will be an issue. If we disagree on something, we are fully capable of talking it out and deciding which solution is best. We could also vote on a scale of 0-3 where 0 is strongly for and 3 is strongly against. Once the total is tabulated, anything less than 4.5 will be going for the strongly for anything greater will be strongly against.

Work Plan

Once we figure out what our building order will be mob programming to begin, then divide up the most important parts for MVP. We will also be coding using the test driven development approach. Our goal is to have an 80% test coverage. We will have a group standup at the beginning of everyday to know what needs to be done for the day.

Git process

We will have one person review the code before merging. We will not work on the master or development branch.

Clone this wiki locally