Skip to content

Team Agreement

Hannah Sindorf edited this page Dec 20, 2018 · 1 revision

Communication Plan

Morning - midday - afternoon standup, where we delegate tasks, communicate blockers, etc. Everyone commits to giving and receiving feedback, including critical

Conflict Plan

If things get stressful, take a break/walk. Express when you're stressed and express conflicts in terms of suggestions for improvement.

Work Plan

Github issues to track tasks - Github project for kanban. Discuss as a group what task each person is going to take. Typically work 9-6

Git process

In a PR:

  • what it does
  • did it break anything
  • did you do testing

At least one other person should review a PR, but all group members should know when there is a merge so they can sync their code.

Modularize code so that it's not all in one file - that way we can be working on different things at the same time without worrying about overlapping.

Etc.

Follow the 15-20 minute guideline for asking for help. Be open to giving help, don't be embarrassed if you need help.

Clone this wiki locally