Triage Bugs

(Activity) for Tier: Sprint

PURPOSE

Triaging bugs is important to identify the next steps in correcting a defect to a work product. Bugs should be triaged continuously to assess their impact to the Sprint and customer expectations. Bugs may apply to multiple types of work product and at minimum apply to development, requirements, documentation, and testing.

WHEN

Continuously throughout the sprint.

PARTICIPATING ROLES

• ACCOUNTABLE

  • Scrum Master

• RESPONSIBLE

  • Project Manager
  • Test Manager
  • Lead Developer
  • Solution Architect
  • Product Owner

INPUTS

• Bugs

ENTRY CRITERIA

Todo

Need ASG to define entry criteria for this activity.

SUB-ACTIVITIES

1. Analyze Bug Source

   • Determine the source of the bug. Some offline investigation may be necessary. The following are the minimum types of activities a bug may apply to:

     • Development – A bug caused by code or another aspect of the development discipline.
     • Requirements – Bugs relating to requirements development and specifications. Usually an out of date or incorrectly defined requirement.
     • Documentation – Bugs relating to Product Support or CDRL documentation. The documentation doesn’t adhere to expectations or software design.
     • Testing – Bugs relating to testing typically including incorrect test cases or test data.

   • Set the Activity field in the Bug work item.

2. Triage Bug

   • Select a team member to assign the bug to based on the activity. For example, Development bugs should be assigned to Development while Requirements bugs are assigned to Product Management.
   • Select the appropriate iteration path. The team may triage bugs within the sprint, to the product backlog, or to a future sprint as a notional plan.

OUTPUTS

• Bugs

EXIT CRITERIA

Todo

Need ASG to define exit criteria for this activity.

NEXT ACTIVITY

• Analyze Test Results

Process Guidance Version: 10.4