Configuration Management
Issue Tracking
Issue Reports
|
Quality Report: Transition Summary
| Purpose |
- This report is essential for looking at what individual contributors are doing within your issue tracking system. All other reports focus on the current state of an issue. This report focuses on who is moving issues from one state to another.
|
| Benefits |
- Provides a high-level overview of what your staff is actually doing.
|
| Drawbacks |
- There is a considerable amount of legitimate work in an SDLC that does not actually impact defect transitions. For example, research, documentation, and design efforts all take time, but don't change defect states.
- A single issue that gets "bounced" between one state and the next may artificially inflate certain transition efforts.
- Despite the appearance of lots of work, this chart hides the presence of any backlog that still remains with any staff. (See Staff Workload)
|
| Explanation |
In the chart below:
Vince is a manager... Lots of triage (review)
Yuriy is a tester... most of her work is logging and verifying fixes.
Sid is a developer... most of his work is fixing bugs. |
|
