ubuntu-defect-analysts team mailing list archive

[Kate Stewart <kate.stewart@xxxxxxxxxxxxx>]

There has been some confusion occurring about the role and
responsibilities of defect analysts on specific teams, and how a team
with defect analysts should be interacting with teams without defect
analysts.

For teams without defect analysts, the follow role should be performed
by the team lead or manager (or their visible delegate ;) ).

The following is a first pass at clarifying the Role and
Responsibilities that has been worked up with the existing Defect
Analysts.  Feedback is welcome. 

Role: 
Analyze defects reported about a team’s packages that are most important
for the quality of the release and customer perception, and ensure that
the defects are addressed by the engineering team.  This requires
creating and maintaining metrics for determining the quality of products
and effectiveness of processes.

Responsibilities:
- Drive and own strategies for assessing the state of their product and
measuring improvements or failures.
- Analyze bugs found and filter out key ones to be worked on by
developers to satisfy milestone targets [1].  
- Clarify and track the handoff process for bugs that transition between
teams.
- Create tools and processes to improve efficiency and utility of the
defect analysis and reporting process,  including development of
appropriate metrics and data visualization.
- Analyze and monitor the bug reporting process of their product to
ensure necessary information is being gathered and that unnecessary bugs
are not being reported.
- Fixing bugs that are important to the analysis and monitoring
processes.

Comments?  Questions?

Thanks, Kate


[1] Note: Initial tooling in place to support analysis of those found by
QA testing, ISO testing.  The capability to do analysis to other classes
of bugs, will be extended as tooling to support the analysis is
developed.