DCI's Critical
Metrics Reports
Too much data. Too little insight.
Just like too little information, a snow storm of detail - in the wrong
form, out of context and too late to make a difference - leads to poor
decision-making.
In
the face of funding cuts and demands for more information IT projects
and services are struggling to make more efficient use of their resources.
There has never been a stronger need for good information to make good
decisions quickly. 
How do you make that
information easily accessible to senior managers, the project team, and
third parties, like project stakeholders? By transforming data into information.
By branding data with clear,
crisp visuals, you can make the information accessible to a wide audience,
and focus them on your story rather than just a series of numbers.
Using project metrics and summarizing
them in visualizations provides significant value in both data analysis
and in communication of results to all stakeholders across the organization.
DCI
helps your managers establish regular Critical Metrics Reports,
plugging in measures of your organization's goals, and sets up data collection
channels within your business processes.
We take the data collected, identify trends and trouble spots, and synthesize
it into usable management information.
The Critical Metrics Report
enhances communication and consensus because it pinpoints problems and
improvement opportunities. It provides objective information --and that
becomes a basis for fact-based decisions.
At
a glance, managers can assess resource loads, backlogs, tasks that lag
behind schedule, and types and locations of defects to track performance,
identify bottlenecks, and identify error-prone modules.
These insights can trigger
immediate changes that improve operations.
The Critical Metrics Report
enables rapid assessment and action against critical project or service
data, whether problem resolution rates, risk management effectiveness,
task completion data, or defect data analysis.
With visuals tailored to meet decision requirements, the value is significant.
For example, visual defect data analyses result in better forecasts of
actual ship dates, providing a more accurate forecast of additional revenue
or other benefits expected from the project's successful implementation.
If you think you could benefit from a DCI Critical Metrics Report
please contact
us now.
Schedule example:
Milestone
|
Original
Plan Date
|
Current/Last
Plan Date
|
Actual
Date
|
Requirements
Signed Off |
1/22/99
|
1/22/99
|
1/22/99
|
Architecture
Document Complete |
2/25/99
|
3/12/99
|
3/15/99
|
Design
Signed Off |
2/28/99
|
3/30/99
|
3/28/99
|
Test
Plans Signed Off |
4/21/99
|
4/21/99
|
4/20/99
|
Feature
Freeze |
6/30/99
|
6/30/99
|
|
Alpha
Candidate to Testing |
7/17/00
|
7/17/00
|
|
Alpha
Docs Review Complete |
7/21/99
|
7/21/99
|
|
UI
Freeze |
8/12/99
|
8/18/99
|
|
Beta
Candidate to Testing |
8/23/99
|
8/23/99
|
|
Code
Freeze |
9/1/99
|
9/1/99
|
|
Beta
Docs Available |
9/5/99
|
9/5/99
|
|
Production
Candidate to Testing |
9/7/99
|
9/7/99
|
|
Support
Training Complete |
9/12/99
|
9/12/99
|
|
Certified
Product Released |
9/21/99
|
9/21/99
|
|
ProductIinstalled
in Production Staging Area |
9/23/99
|
9/23/99
|
|
Product
in Full Production Environment |
9/27/99
|
9/27/99
|
|
Outstanding
Issues for Management Attention: |
|
|
1.
Number of Enhancement Requests/change requests continues to grow;
seems original requirements were insufficient. |
|
2.
Fulfilling Enhancement Requests for added features would extend RTM
to 12/15/99 |
|
3.
"Emergency" fixes for customers are eating up Dev and Tester
time. Next week's report will show expected impacts. |
Note: The various charts
are taken from separate projects, and they do not reflect the same project
or timeframe.
|