Process, Risk Planning, Planning Sprints - Swent-Fall-2024-team-10/leazy GitHub Wiki

Initial Setup

What have been done prior to the meeting:

  • Set up Team Communication
  • Set up GitHub
  • Initialize the Project
  • Set up a Scrum Board
  • Set up CI
  • Set up Figma

During the meeting we reviewed all requirements given in the warmup.

1. Define Process

  • Code review and Pull Request policy: we decided to follow these guidelines from last semester.

  • Protocol for complex merges or potential conflicts: Meeting via Google Meet or in-person.

  • Branch naming convention:

    1. Feature Branches: These branches are used for developing new features. Use the prefix feature/. For instance, feature/login-system.
    2. Bugfix Branches: These branches are used to fix bugs in the code. Use the prefix bugfix/. For example, bugfix/header-styling.
    3. Hotfix Branches: These branches are made directly from the production branch to fix critical bugs in the production environment. Use the prefix hotfix/. For instance, hotfix/critical-security-issue.
    4. Release Branches: These branches are used to prepare for a new production release. They allow for last-minute dotting of i’s and crossing t’s. Use the prefix release/. For example, release/v1.0.1.
    5. Documentation Branches: These branches are used to write, update, or fix documentation. Use the prefix docs/. For instance, docs/api-endpoints.
  • Stand-Up meeting schedules: Monday 15:00-16:00 and Thursday 13:00-14:00.

  • Time budget: we can't currently establish one for everyone

  • Scrum Master and Product Owner assignments for the project:

2. Risk planning

3. Plan Sprint 1

We assign everyone tasks for Sprint 1. Here is a recap: