Sprint Workflow

Under an adapted Scrum methodology, work begins in the Product Backlog. At the start of each sprint, the team selects relevant work from the Product Backlog and moves it into the Sprint Backlog.

Sprint work is divided into five areas of responsibility, matching the five team members. A randomiser is used to assign responsibilities fairly; these can change between sprints and are not permanent roles. During Sprint Planning, each team member takes responsibility for the tasks in their assigned area.

This process distributes work fairly and reduces the chance that the same people repeatedly receive the same type of work. It also makes sprint responsibility visible before implementation starts, which helps the team identify gaps, blockers, and dependencies early.

Trello Sprint Workflow

Each sprint is tracked on the team's Trello board:

Toodle Trello board

The sprint workflow uses these columns:

Sprint Backlog
      |
      v
To Do
      |
      v
In Progress
      |
      v
Testing
      |
      v
Done

The board also includes a Meetings column.

Tasks first enter the Sprint Backlog. Planned work is moved into To Do. When a team member starts a task, the card moves to In Progress. Completed implementation moves to Testing. Once the task has been checked and accepted, it moves to Done.

Cards must be moved continuously as work progresses so the team can see the current state of work at any time. This matters for dependencies: if one task depends on another, the developer can see whether the required task is still in progress, already in testing, or complete before starting dependent work.

Meetings, Check-ins and Stakeholder Interaction

Each sprint has a Meetings column on Trello. Meeting cards contain meeting minutes, screenshots or evidence, progress discussions, blockers, task dependencies, planning decisions, Sprint Review notes, retrospective notes, and stakeholder or client discussions where applicable.

The team does not duplicate all meeting minutes in this documentation site. The Trello board is the supporting record for meeting cards, minutes, screenshots, and stakeholder interaction evidence:

Toodle Trello board

Textbook daily stand-ups are adapted into a few informal team check-ins per week because team members have different class schedules. These check-ins are used to confirm progress, identify blockers, and coordinate dependent tasks.

Sprint Reviews are used to look at completed work and confirm whether sprint goals have been met. Retrospectives are used to reflect on what worked, what did not work, and what should change in the next sprint.

Stakeholder meetings are used to clarify requirements, review progress, discuss technical decisions, receive feedback, and agree on changes. Stakeholder evidence is kept on Trello using this flow:

Stakeholder feedback
        |
        v
Decision
        |
        v
Trello task/card
        |
        v
Implementation
        |
        v
Review or retest