THINK FIRST·CODE LATER

← All labs
S5.5 Review Chapter 5

Team charter and collaboration rules for StudyBuddy

Problem

Write the StudyBuddy team charter — a one-page agreement the five members sign in week 1:

  1. Roles — who is Product Owner, who covers backend/mobile/testing/UX, how the Scrum Master role rotates, who is the backup for each area (think bus factor).
  2. Communication — channels, response times, when to meet, how decisions are made and recorded.
  3. Git workflow — branch naming, PR size, who reviews, what CI must check before merge, how main is protected.
  4. Code-review checklist — 6–8 questions a reviewer must answer.
  5. Conflict and problems — what happens when someone misses deadlines, when people disagree, how to raise a problem early (psychological safety).
  6. AI usage — link to the AI policy (Chapter 2, S2.6) and one rule about knowledge sharing for AI-generated code.

Work it out on paper, in a document or here, then compare with the model answer. Your answer stays in your browser — it is never sent to or stored on the server.

← S5.4 Risk register: exposure and priorities S5.6 Plan the first release with velocity and risks →