Team Charter - AvengerDisassemble/KU-connect GitHub Wiki

Development process

  • The development shall follow the Unified Process, which shall consist of multiple iterations within each phase.
  • There shall be two product owners overseeing the development backlog. These two product owners shall decide on feature addition or removal.
  • There shall be no scrum master; therefore, the responsibility of keeping the process together shall be rested upon every team member.
  • Each sprint shall consist of two weeks.
  • The majority of the team members must agree upon any major decision to become effective. However, if there is a prolonged disagreement, the project manager shall make the final decision.
  • The development process shall be followed strictly, but the workflow shall be subject to the additional team agreement.
  • The development process and workflow can be changed later in the development. The development process must only be changed during the sprint planning or retrospective meeting. However, the workflow can be changed in any meeting.
  • An emergency meeting can be called by anyone with 6 hours' prior notice.

Workflow

  • Communication between team members is highly encouraged.
  • There will be 4 meetings for each sprint, 2 on Wednesday and 2 on Sunday at 8:00 pm.
  • The Wednesday meeting will be about the progress and helping each team member to overcome any problems or blockers, similar to a daily scrum. The meeting will also be timeboxed for 30 minutes.
  • The Sunday meeting at the end of each sprint will consist of sprint planning and retrospective. The Sunday meeting in the middle of the sprint will be about the progress, process, and document review.
  • The date and time of these meetings are flexible and must be adjusted to fit the team member's time.
  • The main branch in GitHub shall only host working code. Under no circumstances shall it be directly committed to.
  • Any suggestions are welcome with open arms. They can be posted in the Discord server.
  • The meeting will be facilitated by the project manager (team lead).
  • Every meeting must have an agenda and minutes listed out at least a day before to ensure effectiveness.
  • On the criteria acceptance, everyone will initially assess their criteria and move their task from 'in progress' to 'review'. The more in-depth criteria review will be performed by another person.
  • One person should not review more than 2 tasks at a time.

Tools and Platforms

  1. Line: For scheduling meetings and communication. This is the preferred channel.
  2. Discord: Discussion and process suggestions
  3. GitHub: Source code management, technical suggestions, and issue tracking
  4. GitHub Project: Task tracking and project planning
  5. GitHub wiki: Documentation
  6. Google Calendar: Keep track of meetings (including meeting minutes and agendas) and events