Generate Agile Metrics Dashboards

The Agile Metrics Dashboard Agent designs, implements, and optimizes dashboards that deliver actionable insights for Scrum teams, product managers, and stakeholders. It tracks velocity, cycle time, work-in-progress, defect density, technical debt ratio, and other key Agile performance indicators, presenting complex project data as clear, practical visualizations with statistical modeling.

Use this agent when you need to monitor sprint health in real-time, calculate velocity statistics for upcoming sprints, identify bottlenecks in your development workflow, or create role-specific dashboard views for different stakeholders. It's ideal when you want to catch sprint risks 3-5 days before sprint end or track technical debt ratios.

Do NOT use this when your team doesn't consistently track story points or maintain accurate JIRA/Azure DevOps data - the agent requires clean, structured input data to generate meaningful insights. Avoid it if you're looking for waterfall project management metrics or non-Agile workflow tracking.

You provide sprint IDs, JIRA or Azure DevOps configuration, Git repository access, and historical velocity data. The agent returns calculated metrics including story point velocity with trend analysis, burndown charts, cycle time distributions, defect rates, velocity statistics with confidence intervals, and role-based dashboard configurations.

The agent connects to JIRA APIs for real-time story updates and sprint data collection, Azure DevOps for work item tracking, Git APIs for code-level insights, and CI/CD pipeline data to track deployment frequency and build success rates.

Scrum Masters use it to monitor sprint burndown, impediment tracking, and team velocity trends with alerts for scope changes exceeding 20% or velocity drops over 15%. Product Owners leverage it for feature progress tracking and release burnup charts. Development teams rely on it for current sprint progress, code quality metrics, and technical debt tracking.

Here's the core data collection architecture:

// Agile metrics data collector
class AgileMetricsCollector {
  constructor(jiraConfig, gitConfig) {
    this.jira = new JiraAPI(jiraConfig);
    this.git = new GitAPI(gitConfig);
    this.metrics = new Map();
  }

  async collectSprintMetrics(sprintId) {
    const sprint = await this.jira.getSprint(sprintId);
    const stories = await this.jira.getSprintStories(sprintId);
    
    return {
      velocity: this.calculateVelocity(stories),
      burndown: this.generateBurndownData(sprint, stories),
      cycleTime: this.calculateCycleTime(stories),
      defectRate: this.calculateDefectRate(stories)
    };
  }

  calculateVelocity(stories) {
    return stories
      .filter(story => story.status === 'Done')
      .reduce((sum, story) => sum + story.storyPoints, 0);
  }

  calculateCycleTime(stories) {
    return stories.map(story => {
      const startTime = new Date(story.transitions.find(t => t.to === 'In Progress').created);
      const endTime = new Date(story.transitions.find(t => t.to === 'Done').created);
      return (endTime - startTime) / (1000 * 60 * 60 * 24); // days
    });
  }
}

The agent implements data validation rules to catch inconsistent story point estimates, uses statistical outlier detection for anomalous metrics, and caches frequently requested metrics with appropriate TTL settings for performance optimization.