Governance Metrics

Collaboration Cycle Activity by Quarter (most recent: 2025Q3)

Shows governance activity including touchpoints completed, products shipped, and staging review issue patterns over time

Touchpoint Types Breakdown

Breakdown of the specific types of touchpoints held during each quarter.

Cycle Time Statistics by Fiscal Year

Data Sources and Definitions

This governance data is collected from the va.gov-team repository where VFS teams track their Collaboration Cycle participation.

Metric Definitions

• Touchpoints Held: Total collaboration cycle touchpoints conducted by the governance team in the quarter. This is the sum of Design Intent reviews, Midpoint reviews, and Staging reviews (issues with "governance-team" label plus specific touchpoint type labels that were created in the quarter)
• Staging Review Findings: Total feedback issues filed during Staging Review process with labels "CC-Dashboard", "Staging", and "collab-cycle-feedback" created in the quarter. Each issue represents a specific finding or recommendation from the governance team
• Avg Collab Cycle Time: The average number of days from when a kick-off issue is created to when the "staging-review" label is added to that issue. This metric is calculated across the entire fiscal year (not quarterly) using label timestamp data from the GitHub API. Shows FY2025 data (Oct 2024 - Sep 2025)
• Launch-Blocking Issues: Critical staging review issues that must be resolved before product launch (staging issues that also have the "launch-blocking" label)
• Launch-Blocking Percentage: The percentage of staging review issues that are classified as launch-blocking (launch-blocking issues ÷ total staging issues × 100)

Cycle Time Statistics Definitions

• Teams: Number of unique VFS teams that participated in the collaboration cycle during the fiscal year
• Products: Total number of products that completed the collaboration cycle (from kick-off to Staging Review) during the fiscal year
• Mean: The arithmetic average of all cycle times. Calculated by summing all cycle times and dividing by the number of products. All values are shown in days
• Median: The middle value when all cycle times are sorted from shortest to longest. Half of products took less time, half took more
• Max: The longest cycle time recorded (slowest product through the collaboration cycle)
• Std Dev (Standard Deviation): Measures how spread out the cycle times are from the mean. A higher number indicates more variation in cycle times across teams

Data Collection Process

All metrics are automatically collected using the GitHub API to query issues in the va.gov-team repository based on:

• Issue labels: Specific combinations of labels that identify different collaboration cycle activities
• Date ranges: Issues created or closed within each quarter's date boundaries
• Issue state: Whether issues are open, closed, or created within the time period