Project-level dashboards usually display information about a particular
project. The dashboards are in IBM Cognos Connection, under . The
following dashboards are sample project level dashboards:
- Productivity
- Requirement
- Stakeholder Requirement
- Quality
- Defect
- Defect Detection
- Defect Prevention
Productivity dashboard
The Productivity dashboard
contains metrics showing how productive the team is in delivering
the software. The measures used include project length as a function
of size as well as task completion velocity. The dashboard also includes
schedule performance (SPI) and variance (SI) data to show how work
is tracking to budget and schedule. Use this dashboard as a starting
point for understanding the scope of work, how well it is addressed,
and its progress. This dashboard contains the following reports:
- SPI &SV: The schedule performance index (SPI) measures how
effectively you are using time in an iteration or project. Use it
to identify trends of progress against a plan. The schedule variance
(SV) indicates whether a project is ahead of or behind schedule.
- Build health: This report tracks the health of a product build
over time. It compares the number of time intervals with a failed
build to the time intervals with a clean build.
- Project cycle: This report shows how project length varies with
project size. Use it to estimate how long future projects will take
to complete, and to understand the impact of work efficiency increases
or process improvements.
- Iteration velocity: This report shows the number of tasks completed
in each iteration. Use it to understand how much work can be done
in each iteration cycle. Generally the line should be fairly constant.
Significant increases or decreases can indicate external pressures
on the project, which should be understood. However, the chart assumes
that all tasks involve roughly the same amount of work. Defining tasks
with significantly more or less work can impact the number of tasks
completed within a fixed time period.
- Project length: This report shows the length of each project (in
months). Use it to help identify projects that might need attention
because they are taking significantly more or less time than the others.
Requirement dashboard
Managing requirements
is an essential process for an efficient project. Because requirements
can be submitted at any time and can change, the team needs to respond.
Use the Requirement dashboard to evaluate how effective the team is
at satisfying requirements, controlling the amount of change, and
responding to requests promptly. This dashboard contains the following
reports:
- Enhancement request backlog: This report monitors the average
number of enhancement requests that are received and closed over time,
and the number of outstanding enhancement requests. This data contributes
to the enhancement request backlog for each project.
- Requirement churn: This report indicates the trends in changes
to the definition of system requirements. It also provides insight
into the stability of system definition for a product.
- Requirement distribution by status: This report shows the growth
of requirements by status. It provides insight into the maturity level
of the system definition. It also characterizes the stability and
completeness of system requirements, with potential impacts on design
and production.
Stakeholder requirement dashboard
The Stakeholder
Requirement dashboard shows metrics showing how effective the team
is at satisfying functional requirements. The measures included in
this dashboard allow you to track requirements changes, monitor and
manage enhancement requests, and monitor the quality of requirements
being delivered. This dashboard contains the following reports:
- Enhancement request backlog: This report monitors the average
number of enhancement requests that are received and closed over time,
and the number of outstanding enhancement requests. This data contributes
to the enhancement request backlog for each project.
- Requirement churn: This report indicates the trends in changes
to the definition of system requirements. It also provides insight
into the stability of system definition for a product.
- Requirement distribution by status: This report shows the growth
of requirements by status. It provides insight into the maturity level
of the system definition. It also characterizes the stability and
completeness of system requirements, with potential impacts on design
and production.
- Test coverage of requirements: This report makes sure that all
requirements are validated and that the product works as intended.
- Defects per requirement: This report indicates the quality of
code for each requirement type.
Quality dashboard
The Quality dashboard presents
information indicating a project's quality. Overall quality is
indicated by the number of defects relative to project size, defect
backlog, defect repair latency, plus how responsive the team is to
enhancement requests. This dashboard contains the following reports:
- Defect density by severity: This report indicates the quality
of code attained during development across a project and each deliverable,
based on the relative number of defects and code size. This data contributes
to the defect density by severity for each project.
- Defect distribution by severity: This report shows the total number
of defects for a given project. The defect totals indicate components
that are defect-prone.
- Defect backlog: This report indicates the number of defects during
development, based on defect status. You can see how many defects
remain in the system. This data contributes to the defect backlog
for each project.
- Enhancement request backlog: This report monitors the average
number of enhancement requests that are received and closed over time,
and the number of outstanding enhancement requests. This data contributes
to the enhancement request backlog for each project.
- Test execution status: This report indicates whether planned tests
are complete or outstanding. The testing success rate reflects whether
the system is working correctly.
Defect dashboard
The Defect dashboard shows
defect-related metrics intended to highlight project quality. The
pre-ship to post-ship breakdown helps you determine how effective
internal testing is, how responsive the team is, and how effectively
defects are resolved. These measures are all important in evaluating
the overall quality of a project. This dashboard contains the following
reports:
- Defect backlog: This report indicates the number of defects during
development, based on defect status. You can see how many defects
remain in the system. This data contributes to the defect backlog
for each project.
- Defect density by severity: This report indicates the quality
of code attained during development across a project and each deliverable,
based on the relative number of defects and code size. This data contributes
to the defect density by severity for each project.
- Project burndown: A burndown chart shows the team's progress.
It shows a trend view of tasks being assigned and completed during
a given time.
- Test coverage of requirements: This report makes sure that all
requirements are validated and that the product works as intended.
- Test execution status: This report indicates whether planned tests
are complete or outstanding. The testing success rate reflects whether
the system is working correctly.
Defect detection dashboard
The Defect Detection
dashboard shows the metrics related to defect prevention. This dashboard
monitors how effective and efficient the team is in preventing defects.
A high number of defects during development and poor build health
are good indicators of poor defect prevention. This dashboard contains
the following reports:
- Defect backlog: This report indicates the number of defects during
development, based on defect status. You can see how many defects
remain in the system. This data contributes to the defect backlog
for each project.
- Defect distribution by severity: This report shows the total number
of defects for a given project. The defect totals indicate components
that are defect-prone.
- Defect density by severity: This report indicates the quality
of code attained during development across a project and each deliverable,
based on the relative number of defects and code size. This data contributes
to the defect density by severity for each project.
- Test coverage of requirements: This report makes sure that all
requirements are validated and that the product works as intended.
- Test execution status: This report indicates whether planned tests
are complete or outstanding. The testing success rate reflects whether
the system is working correctly.
- Code churn: This report shows the volume of changes in a project
over time. An upward slope is normal through the early and middle
stages of a project. As the project nears completion, the curve should
slope downward. An upward slope late in a project might indicate that
the project is not stabilizing.
- Build health: This report tracks the health of a product build
over time. It compares the number of time intervals with a failed
build to the time intervals with a clean build.
Defect prevention dashboard
The Defect Prevention
dashboard shows the metrics related to defect detection. This dashboard
monitors how effective and efficient the team is in detecting defects.
A high number of post-ship defects and low test coverage are good
indicators of poor defect detection. This dashboard contains the following
reports:
- Defect backlog: This report indicates the number of defects during
development, based on defect status. You can see how many defects
remain in the system. This data contributes to the defect backlog
for each project.
- Defect distribution by severity: This report shows the total number
of defects for a given project. The defect totals indicate components
that are defect-prone.
- Defect density by severity: This report indicates the quality
of code attained during development across a project and each deliverable,
based on the relative number of defects and code size. This data contributes
to the defect density by severity for each project.
- Build health: This report tracks the health of a product build
over time. It compares the number of time intervals with a failed
build to the time intervals with a clean build.
- Fixes failing verification: This report indicates the percentage
of defects with reports of fixes that fail verification tests.