Difference between revisions of "INSUFFICIENT METRICS"
Jump to navigation
Jump to search
(Created page with "<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.........................................................................................") |
m (empty lines removed) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Process Issues]] / Back to [[Test Automation Issues]]</span> | <div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Process Issues]] / Back to [[Test Automation Issues]]</span> | ||
| − | =<span style=" | + | =<span style="font-size: 16px">'''Issue Summary'''</span>= |
| − | + | <span style="font-size: 16px">Few or no metrics are collected or not consistently. Collection is cumbersome.</span> | |
| − | =<span style="font-size: 16px">Category</span>= | + | =<span style="font-size: 16px">'''Category'''</span>= |
| − | <span style="font-size: 16px">Process</span | + | <span style="font-size: 16px">Process</span><span style="font-family: Arial; font-size: 16px"> </span> |
| − | =<span style=" | + | =<span style="font-size: 16px">'''Examples'''</span>= |
| − | |||
| − | |||
# <span style="font-family: Arial; font-size: 16px">Metrics are collected from different systems and have to be consolidated manually.</span> | # <span style="font-family: Arial; font-size: 16px">Metrics are collected from different systems and have to be consolidated manually.</span> | ||
# <span style="font-family: Arial; font-size: 16px">The collected metrics are not the metrics that are needed by management.</span> | # <span style="font-family: Arial; font-size: 16px">The collected metrics are not the metrics that are needed by management.</span> | ||
# <span style="font-family: Arial; font-size: 16px">Metrics can only be collected after they have lost most of their importance.</span> | # <span style="font-family: Arial; font-size: 16px">Metrics can only be collected after they have lost most of their importance.</span> | ||
| − | + | =<span style="font-size: 16px">'''Questions'''</span>= | |
| − | =<span style=" | + | <span style="font-family: Arial; font-size: 16px">What metrics are collected?</span><br /> <span style="font-family: Arial; font-size: 16px">Which metrics does management need?</span><br /> <span style="font-family: Arial; font-size: 16px">Who collects the metrics? When?</span><br /> <span style="font-family: Arial; font-size: 16px">In what form are they saved?</span><br /> <span style="font-family: Arial; font-size: 16px">Can the collection and/or presentation of the metrics be automated?</span> |
| − | + | =<span style="font-size: 16px">'''Resolving Patterns'''</span>= | |
| − | + | <span style="font-family: Arial; font-size: 16px">Most recommended:</span><br /> | |
| − | =<span style=" | ||
| − | |||
| − | |||
* <span style="font-family: Arial; font-size: 16px">[[SHARE INFORMATION]]: This pattern is important if you do not really know what metrics are needed (management, development, maintenance etc.)</span> | * <span style="font-family: Arial; font-size: 16px">[[SHARE INFORMATION]]: This pattern is important if you do not really know what metrics are needed (management, development, maintenance etc.)</span> | ||
* <span style="font-size: 16px">[[ AUTOMATE THE METRICS]]</span><span style="font-family: Arial; font-size: 16px">: Apply this pattern if you need consistent and reliable metrics. It is most necessary for large testing efforts and not only for automation. For small projects it could become an overkill</span> | * <span style="font-size: 16px">[[ AUTOMATE THE METRICS]]</span><span style="font-family: Arial; font-size: 16px">: Apply this pattern if you need consistent and reliable metrics. It is most necessary for large testing efforts and not only for automation. For small projects it could become an overkill</span> | ||
<br /> <span style="font-size: 16px">Other useful patterns:</span><br /> | <br /> <span style="font-size: 16px">Other useful patterns:</span><br /> | ||
| − | + | * <span style="font-size: 16px">[[SELL THE BENEFITS]]: This pattern will help you get support to [[AUTOMATE THE METRICS]]</span> | |
| − | * <span style="font-size: 16px">[[SELL THE BENEFITS]]: This pattern will help you get support to[[ | ||
<span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Process Issues]] / Back to [[Test Automation Issues]]</span></div> | <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Process Issues]] / Back to [[Test Automation Issues]]</span></div> | ||
Latest revision as of 06:35, 5 May 2018
.................................................................................................................Main Page / Back to Process Issues / Back to Test Automation Issues
Issue Summary
Few or no metrics are collected or not consistently. Collection is cumbersome.
Category
Process
Examples
- Metrics are collected from different systems and have to be consolidated manually.
- The collected metrics are not the metrics that are needed by management.
- Metrics can only be collected after they have lost most of their importance.
Questions
What metrics are collected?
Which metrics does management need?
Who collects the metrics? When?
In what form are they saved?
Can the collection and/or presentation of the metrics be automated?
Resolving Patterns
Most recommended:
- SHARE INFORMATION: This pattern is important if you do not really know what metrics are needed (management, development, maintenance etc.)
- AUTOMATE THE METRICS: Apply this pattern if you need consistent and reliable metrics. It is most necessary for large testing efforts and not only for automation. For small projects it could become an overkill
Other useful patterns:
- SELL THE BENEFITS: This pattern will help you get support to AUTOMATE THE METRICS