Skip to content

Team Charter

Jump to bottom
Loic Nyssen edited this page Mar 11, 2018 · 4 revisions

Software development Project NES-NN

Team Mission and Objectives or Goals

Team Purpose

  • To complete ITC303 & ITC306 with the goal of a HD mark
  • To create and train a Neural Network project.

Duration and Time Commitment

  • Attend meetings every fortnight on Sunday at 6:30pm AEST, allocate minimum 1 hour of time to meeting, expected absences/tardiness preferred minimum 3 days notice to allow for rescheduling. Unexpected absences/tardiness to meetings must be notified ASAP.

Members

  • Loic Nyssen
  • Joshua Beemster
  • Jasim Schluter

Role Identification

  • To be fair to all team members, all team rolls will be rotated at each project milestone.

Scope

  • To meet requirements and not go unreasonably beyond them
  • Unreasonably to be decided by majority vote

Record

  • Meetings will be held over voice chat, and meeting minutes will be recorded by using a shared Google Docs Document and then published to the wiki when completed
  • All communication will occur via chat in Discord, which automatically records chat history
  • All collaboration for documents will be performed in Google Docs where all team members have access, then published to the Wiki upon completion
  • All wiki documentation must be agreed upon by majority before posting
  • GitHub will be used for code version control
  • All code changes should be thoroughly documented in commits to Git.
  • Commits should be small enough that the changes can be thoroughly documented in a couple of sentences at most
  • Code review may occur over voice chat between Author and Reviewer. However upon any form of conflict the appointed Mediator must become involved before continuation of arguments. All agreements resolved from dispute must be documented into Discord text chat for record keeping

Agreements

  • All disputes to be resolved with a vote where a majority rules
  • All team members agree to follow majority rulings
  • All disputes which are put to formal vote must be documented
  • Team members must be given a minimum 12 hours of available time to respond to a formal vote via email.
  • When majority is not available disputes to be resolved by a best-of-three scissors paper rock
  • Team members will check Discord as often as possible and respond with an answer or a message to tell other members they don’t know
  • Poor team performance such as low quality of work, not attending meetings or not being available for long periods of time without notice will be resolved with a three strike policy. A strike requires a majority ruling.
  • On the occurrence of a team member receiving three strikes, the issue will be reported to Dr James Tulip immediately
  • If any team member is having an issue that could affect their ability to meet deadlines, they will notify and also ask other team members for help as soon as possible
  • When work has been completed, it must be pushed to GitHub immediately (in the team member’s personal branch), and other team members must be notified via Discord
  • When work is completed by a team member, it must be reviewed and deemed satisfactory by a majority before being merged to ‘master’ branch
  • All code must be written to exact C# Style Guide specification with no leniency unless agreed upon by majority
  • Under no circumstances should you git rebase - we cannot rewrite history.
  • Code must be reviewed within 48 hours of request

Sign Off:

I have participated in the development of this charter and agree to it.

Team Member: Loic Nyssen Team Member: Joshua Beemste Team Member: Jasim Schluter

Date: 11th of March 2018

Clone this wiki locally