Skip to content

Issue Triage and Backlog Refinement

Jump to bottom
A.J. Stein edited this page Sep 21, 2023 · 4 revisions

Summary

Issue Triage versus Backlog Refinement

Issue Status from Triage to Refinement to Completion

flowchart TD
    NT[Needs Triage] -->|triage in weekly meeting| FAN[Further Analysis Needed]
    FAN --> AR{devs analyze 1-4 hours and decide to}
    AR -->|refine and prune issues| NR[Needs Refinment]
    AR -->|accept issue| T[Todo]
    AR -->|request deep research| DRN[DEFINE Research Needed]
    AR -->|seek volunteer| VN[Volunteer Needed]
    NR -->|break down issues| NP[Needs Pruning]
    NP -->|triage pruned issues| NT
    NR -->|accept refined issue| T
    DRN -->|research refines and creates new issues| NT
    VN -->|volunteer picks up work until complete| INP
    T -->|add issue to sprint| INP[In Progress]
    INP --> BOC{work until blocked or complete}
    BOC --> |complete tasks, request review| UR[Under Review]
    BOC --> |inform team issue is blocked| B[Blocked]
    B -->|work with team to unblock and resume progress| INP
    UR -->|devs review to approve or reject| RA[Reviewer Approved]
    RA -->|change merged into release or site| Done
Loading

NOTE: This information exists for the benefit of NIST staff. Although the community may reference or inquire about content, this material is not explicitly intended for community support. The community may create issues to report bugs or request enhancements related to this documentation, but there is no support guarantees for this material. All issues will be considered on a case by case basis.

Standard Operating Procedures

Developer Knowledge Base

Team Members' Responsibilities

Clone this wiki locally