Skip to main content

Project Health Metrics Guide

Core Metrics Overview​

Velocity Metrics​

MetricDefinitionTargetWarningCritical
Sprint VelocityStory points per sprintWithin 10 points of avgWithin 20 points of avgOver 20 points from avg
Completion RateCompleted vs planned workAbove 9070 to 90Below 70
Capacity UtilizationHours utilized vs available70 to 8585 to 95Above 95

Quality Metrics​

MetricDefinitionTargetWarningCritical
Bug CountActive bugs by severityUnder 5 total5 to 10 totalOver 10 total
Code CoverageTest coverage ratioAbove 8070 to 80Below 70
Technical DebtCode needing refactorUnder 55 to 10Above 10

Time Metrics​

MetricDefinitionTargetWarningCritical
Lead TimeIdea to productionUnder 30 days30 to 45 daysOver 45 days
Cycle TimeStart to completionUnder 5 days5 to 10 daysOver 10 days
Review TimePR open to mergeUnder 2 days2 to 4 daysOver 4 days

Data Collection Process​

Daily Metrics Collection​

  1. Bug Tracking

    • Monitor new bugs
    • Track bug severity
    • Update resolution status
    • Identify trends

  2. Build Status

    • CI/CD pipeline health
    • Test coverage reports
    • Build success rate
    • Deployment status

  3. Code Review

    • Open pull requests
    • Review turnaround time
    • Comments resolution
    • Merge success rate

Sprint Metrics Collection​

  1. Team Performance

    • Velocity tracking
    • Story completion rate
    • Sprint goal achievement
    • Team capacity utilization

  2. Quality Indicators

    • Bug detection rate
    • Test coverage changes
    • Technical debt additions
    • Code review effectiveness

Monthly Metrics Collection​

  1. Code Quality

    • Static analysis results
    • Architecture compliance
    • Documentation coverage
    • Security scan results

  2. Team Health

    • Satisfaction surveys
    • Capacity trends
    • Skills development
    • Collaboration effectiveness

Analysis and Action​

Metric Analysis Process​

  1. Data Collection

    • Use automated tools
    • Maintain consistency
    • Validate accuracy
    • Document anomalies

  2. Trend Analysis

    • Track over time
    • Identify patterns
    • Compare with baselines
    • Note correlations

  3. Impact Assessment

    • Evaluate severity
    • Determine scope
    • Assess urgency
    • Consider dependencies

Taking Action​

  1. For Warning Levels

    • Investigate root causes
    • Plan corrective actions
    • Monitor closely
    • Update stakeholders

  2. For Critical Levels

    • Immediate team meeting
    • Rapid response plan
    • Stakeholder communication
    • Daily monitoring

  3. Preventive Measures

    • Process improvements
    • Tool enhancements
    • Team training
    • Resource adjustment

Reporting Guidelines​

Daily Reports​

  • Quick status updates
  • Blocking issues
  • Critical metrics
  • Immediate actions

Sprint Reports​

  • Velocity trends
  • Goal achievement
  • Quality metrics
  • Risk assessment

Monthly Reports​

  • Detailed analysis
  • Trend visualization
  • Recommendations
  • Success stories