Analyze Test Results

(Activity) for Tier: Sprint

PURPOSE

Iteratively analyzing test results can help provide useful information to improve the team’s test approach.

WHEN

Throughout the sprint.

PARTICIPATING ROLES

• ACCOUNTABLE

  • Test Manager

• RESPONSIBLE

  • Test Manager
  • Tester

INPUTS

• Sprint Backlog (User Stories, Bugs, Test Cases, Test Case Review Results, etc.)
• Test Results

ENTRY CRITERIA

Todo

Need ASG to define entry criteria for this activity.

SUB-ACTIVITIES

1. Gather Data For Analysis

   • At a minimum, consider the following:

     • Gather data on results of test execution.

       • For example, test run results for manual, exploratory, regression or automated tests.

     • Gather data on the results of test case peer reviews.

       • For example, was the test accepted ‘as is’, accepted with minor changes, or were major changes needed.

2. Interpret Results and Draw Conclusions

   • Interpret results of test execution.
   • Interpret results of test case peer reviews.

3. Determine Post-Interpretation Actions

   • Once test data has been collected, interpreted, and analyzed:

     • Determine any follow-on actions to be recommended/taken, as applicable.
     • Consider taking these actions to the sprint retrospective, as applicable.

4. Document Analysis Findings

   • Determine a storage location and record conclusions and actions drawn from data, per team procedures.

OUTPUTS

• Test Analysis Results

EXIT CRITERIA

• Test results have been interpreted, conclusions drawn, and recommended actions have been captured.

NEXT ACTIVITY

• Conduct Sprint Review

Process Guidance Version: 10.4