Last updated 16 April 2026

Prioritisation

Prioritisation is used wherever sequencing decisions are made so teams can make consistent trade-offs based on impact, urgency, effort, and risk.

Outcomes

Typical outcomes from prioritisation:

  • Ranked backlog with clear priority order
  • Consistent prioritisation decisions across teams
  • Visibility of trade-offs and deferred work
  • Shared rationale for sequencing decisions

Where It Applies

  • Validation: initial urgency and value signals are assessed as issues enter the pipeline.
  • Planning: cycle-level sequencing is finalised against capacity and delivery goals.

Priority levels

Low

Low-impact ideas, suggestions, or cosmetic fixes that can be taken when the team has free capacity.

Examples:

  • Minor visual issues
  • Optional improvements
  • One-user bugs
  • Long-term “nice to have” ideas

How it is handled

  • Taken only after higher-priority items are completed
  • May be implemented gradually over time

Medium

Enhancements, ideas, or minor fixes that improve experience but are not time-critical.

Examples:

  • UI improvements
  • Non-critical bugs
  • Quality-of-life changes
  • Feature ideas

How it is handled

  • Included across the next 3-4 sprints, depending on capacity

High

Important issues that affect users or business logic but do not block core functionality, including important UI changes and new features.

Examples:

  • Functionality works, but with issues that need timely attention
  • Significant improvements needed soon
  • Features or fixes that are important for the next 1-2 sprints

How it is handled

  • Planned into the nearest upcoming sprints

Urgent

Critical issues that directly impact platform functionality or block users from completing essential actions.

Urgent should be reserved only for truly blocking issues. Ideas, improvements, UI tweaks, and planned work should not be marked as urgent, because this disrupts planning and slows down real critical fixes.

Examples:

  • Payments not going through
  • Patients unable to complete verification
  • Clinical workflow fully blocked
  • Major feature down in production

How it is handled

  • Taken into work immediately (fire line)
  • Pulled into the current sprint or delivered as an out-of-sprint hotfix

Deadline-based work

If something is required by a specific date, please highlight the required deadline inside the issue description. Examples include:

  • Clinic campaign
  • Regulatory change
  • Marketing launch
  • Other time-sensitive changes

This helps us structure the sprint planning correctly and ensure nothing is missed.