Skip to main content

Bug Lifecycle

The lifecycle of an incident (bug) focuses on the reporting, triage, and resolution of defects. Some bugs (critical) require an immediate hotfix, while others can be scheduled in the current or following sprint as a bugfix.

Diagram of the Bug Lifecycle​

Key Steps for Incidents (Bugs)​

  1. Issue Submission

    • Bugs can be reported by users, stakeholders, or through monitoring tools.

  2. Issue Triage & Severity Assessment

    • The team assesses the impact, severity, and potential scope of each bug.

  3. Prioritization Decision

    • Hotfix (Critical Bug): Immediate fix in the current sprint if it severely disrupts functionality.
    • Bugfix (Less Critical Bug): Scheduled for the current or next sprint, depending on capacity.

  4. Implementation & Testing

    • The team develops the solution and performs the necessary tests.

  5. Release to Production

    • The fix is deployed to production once validated (hotfix) or during the sprint’s release.

  6. Post-Release Review

    • It is verified that the fix resolves the issue without introducing new problems.

  7. Rework / Evaluate Complexity

    • If the bug is not completely resolved, it is re-evaluated for further adjustments (either carried over to the next sprint or into the next PI, depending on complexity).