Skip to main content
Version: Sprint 1

Project Methodology

Our team follows an Agile methodology, specifically adopting practices from Scrum (Schwaber & Sutherland, 2020), adapted to a lightweight, weekly-to-biweekly cadence to accommodate variable member availability across coursework. We chose this approach over a more rigid framework like Waterfall because our requirements have evolved iteratively as we've built out the editor, and Scrum's short feedback loops let us adjust task allocation and priorities each sync-up rather than committing to a fixed plan upfront.

1. Agile Framework & Communication​

  • Sprint Meetings: The project follows an iterative Agile methodology, utilizing regular sprint meetings to sync on progress.
  • Team Collaboration: Team communication and screen-sharing sessions (such as reviewing project briefs and extracting requirements) are hosted primarily on Discord.

2. Task & Issue Management​

  • Platform: Gitea is used as the central hub for tracking project milestones, issues, and overall repository management.
  • Categorization: Tasks are actively categorized using labels such as "Documentation" and "Work allocation" to keep the backlog organized.
  • Allocation: Specific issues (like editor styling, deployment, and documentation) are explicitly assigned to team members (e.g., Kauch, altairakami) to establish clear accountability.

3. Version Control & Git Strategy​

  • Branching Model: The team employs a structured branching strategy using prefixes to define the type of work being done, such as feature/ (e.g., feature/machine-parser), refact/ or refactor/ (e.g., refact/visual-editor), fix/, and build/.
  • Integration Flow: Work is not pushed directly to production; instead, branches are merged via Pull Requests into intermediate branches like dev or refact/project-structure before eventually being merged into main.
  • Continuous Integration: The repository utilizes automated CI workflows for deployment and package management tasks, such as adding pnpm installations and deployment pipelines.

4. Documentation Strategy​

  • Centralized Docs: Documentation is treated as a first-class citizen in the development roadmap, tracked via dedicated Gitea issues.
  • Tooling: The team is utilizing Docusaurus to build and maintain the project's formal documentation site.
  • Scope: Documentation deliverables include the project methodology, Git methodology, tech stack details, installation instructions, and architectural diagrams.

Evidence of Use​

Figure 1: Screenshot of Gitea Issues list, showing labelled and assigned tasks Figure 1: Screenshot of Gitea Issues list, showing labelled and assigned tasks

Figure 2: Screenshot of Gitea Pull Requests, showing branch-based merge workflow Figure 2: Screenshot of Gitea Pull Requests, showing branch-based merge workflow

Figure 3: Screenshots of four dated sprint meetings (5, 10, 17, and 23 August 2026), showing full-team attendance

Figure 3a: Sprint meeting, 5 August 2026 Figure 3b: Sprint meeting, 10 August 2026 Figure 3c: Sprint meeting, 17 August 2026 Figure 3d: Sprint meeting, 23 August 2026

As of Sprint 1, our repository shows 22 active issues distributed across team members, 20 merged pull requests following our branching strategy, and four documented sprint meetings held via Discord (5, 10, 17, and 23 August 2026), reflecting sustained engagement with this methodology throughout the sprint.

Reference​

Schwaber, K. & Sutherland, J. (2020). The Scrum Guide. https://scrumguides.org