SDLC Insights
Engineering delivery score, top actions, and module snapshots across your delivery lifecycle.
What SDLC Insights shows
SDLC Insights is a module-based dashboard for platform and engineering leaders. It groups 34 metrics into six areas that match the left navigation in the app:
- DORA Metrics — deployment frequency, lead time, change failure rate, mean time to restore
- CI Pipeline Insights — workflow success rate, duration, flakiness, queue wait, cache hit rate
- Collaboration & PR Metrics — review time, PR size, throughput, and review participation
- Security & Risk Metrics — vulnerability exposure, secret scanning, dependency risk
- Governance & Architecture: policy compliance, architecture drift, and documentation coverage
- Financial & Operational: CI minutes, seat utilization, and API rate-limit consumption
Open Insights → SDLC Insights → Overview, or open a single module from the sidebar (for example DORA Metrics or CI Pipeline Insights).
CI Pipeline Insights answers whether CI has been healthy lately: success rate, duration, flakiness, queue wait, and cache hit rate. It does not decide whether a workflow is configured. That question is Agentic Foundation, on the Continuous Integration rows CI on change, CI runs build, CI runs tests, and CI static analysis, including linked CI templates. A failing Actions run does not rewrite those setup rows. Live charts need GitHub Actions. See Four CI questions.
Agentic readiness measures repo-agent maturity from scans; the engineering delivery score measures live delivery signals from connected integrations.
When no live metrics are available, the executive panel says Connect version control and CI data to activate delivery metrics for this workspace. It does not reuse the Agentic readiness % as the delivery score.
Overview page layout
The overview opens with collapsible sections:
- Engineering delivery score: the average of live metric bands for the selected period (0–100), with a status headline and four summary stats (delivery score, live metrics, modules at risk, coverage). This is not a scan score and not Agentic readiness.
- Status headline: Delivery signals are on track, Some delivery signals need attention, or Delivery risk detected in live metrics. When delivery risk is detected and the /100 number is still mid or high, the panel adds that the /100 number is the average of live metric bands and the headline is the worst live signal, not a second overall score. For example, 83/100 can sit next to Delivery risk detected in live metrics.
- Top actions — up to three prioritized recommendations for the whole workspace.
- Correlated signals — cross-module patterns when the platform detects related issues (for example, elevated change failure rate plus weak CI success).
- Module snapshots — compact chart per module when enough live history exists.
- Explore modules — full module sections with Open module → links to each module page.
Each module page repeats Top actions for this module and a Module summary before the individual metric sections.
What is live in v1
Most metrics need additional integrations or batch jobs. In the current release, six metrics report live values from connected GitHub productivity data when your workspace has PR, CI, and (where applicable) deployment activity in range:
| Metric | Module |
|---|---|
| Deployment Frequency (deployments per day) | DORA Metrics |
| Lead Time for Changes | DORA Metrics |
| Change Failure Rate | DORA Metrics |
| Workflow Success Rate | CI Pipeline Insights |
| PR Time-in-Review | Collaboration & PR Metrics |
| PR Size (Line Delta) | Collaboration & PR Metrics |
Time to Restore Service (MTTR) becomes live when an incident-management integration (PagerDuty, Opsgenie, or GoAlert) is connected and productivity ingest has incident data in range. Until then the card shows Connect to unlock.
Change Failure Rate prefers deployment + incident linkage when that data exists; otherwise it uses GitHub Actions CI failure rate as a proxy.
Live after readiness jobs: Branch protection compliance, documentation health, stale branches, inactive/orphaned repos, and Dependabot backlog (readiness proxy) show as Live or Connect to unlock once the governance auditor has run and GitHub is connected. Those cards are not the workspace Agentic readiness %. Financial metrics are live. Each expanded row keeps the GitHub chip as Connected and explains the read permission underneath. Copilot seat utilization stays empty when the org has no seats. Remaining catalog metrics show Coming soon until their ingest pipelines ship.
Deployment Frequency is shown as deployments per day. It can come from GitHub Deployments or monitoring deployment markers (New Relic / Grafana). Lead Time for Changes still needs GitHub PR ↔ deploy linkage; monitoring alone does not unlock it.
Metric status labels
Each metric section shows a status in the header:
| Label | Meaning |
|---|---|
| Live | The platform computed a value from connected integrations for the selected period. Trend and benchmark bands appear when enough history exists. |
| Coming soon | The metric is on the roadmap but not yet available from your connected data. |
| Connect to unlock | A specific integration is required (for example GitHub Actions, PagerDuty, or a readiness scan). Use the integration chips or View integrations to open Workspace → Integrations. |
| Demonstration data | Shown only when the SDLC API is unavailable (for example local preview). Values are illustrative, not from your workspace. |
Benchmark bands use Elite / High / Medium / Low. Open How we compare on the overview or a module page for definitions.
Filters
Use the toolbar above the page to scope the view:
- Time range: 7, 30, 90, or 180 days, or a custom range.
- Department / team: Same Insights filter bar as other Insights pages — apply filters before charts load.
Trend deltas compare the selected window to the prior period of equal length (for example, last 30 days vs the 30 days before that).
Banner on the overview
Only Insights → SDLC Insights → Overview shows a banner for the GitHub delivery pipeline. It appears while that pipeline is Backfilling, Not started, still refreshing, Failed, or has stale or missing days in its window. DORA, CI, and the other module pages leave this banner off.
Backfilling includes a progress percent when one is available. There is no estimated time remaining. Failed, stale, and missing days include a link to Data coverage for this pipeline (/workspace/data-coverage?pipeline=sdlc_github). The overview filter and charts stay available, and the banner remains while the gap is active. No banner appears when the pipeline is complete and current, when the workspace has no pipeline of this kind, or when the coverage request is still loading or has failed. Every role that can open the overview sees it.
Integrations
Locked metrics link to Workspace → Integrations with a return path back to SDLC Insights. Integration chips deep-link to the relevant section (source control, CI/CD, AI tools, or monitoring). A source that is already connected shows as Connected and does not link to the connect flow. On a financial metric, a sentence under GitHub Connected names the read permission that fills it. API rate limit says no extra permission is required.
Expand a locked metric to see what to do next:
| Badge | What it means |
|---|---|
| Integration required | That source is not connected. Use Connect to open the matching integrations section. |
| Setup needed | GitHub is connected, but a product or app permission is still off. The button opens that GitHub page. |
| Waiting for data | The source is connected and a sync is still running. GitHub and CI history usually starts within a few hours. A full 180-day history can take longer. Security, governance, financial, and rollup metrics refresh once a day at 04:00 UTC. |
| Refresh incomplete | The last refresh did not finish, and a successful one is still less than two days old. The next try is 04:00 UTC. You do not need to reconnect. |
| Refresh failing | Refreshes have been failing for at least two days, or this refresh has not succeeded yet. You do not need to reconnect. |
| No data in this range | The sync is current and there is no activity in the selected period. Governance metrics that depend on a readiness scan say to run one in Agentic Foundation. |
Workspace admins can open View data coverage from these rows. Other members see the same explanation without that link.
Security and financial GitHub metrics also need optional Insights setup in Connect GitHub (per organization: App permissions, Code security products, and plans). There is no separate GitHub Advanced Security connector.
Typical data sources by module:
| Module | Typical integrations |
|---|---|
| DORA Metrics & CI Pipeline Insights | GitHub, GitHub Actions |
| Collaboration & PR Metrics | GitHub |
| Security & Risk Metrics | GitHub Dependabot and secret scanning after optional Insights setup |
| Governance & Architecture Metrics | GitHub; some signals also need an Agentic Foundation readiness scan |
| Financial & Operational Infrastructure | GitHub. Under Connected, each metric says which read permission fills it: Organization administration, GitHub Copilot Business, Members, Actions and Deployments, or Contents. API rate limit needs no extra permission. |
| Time to Restore Service (MTTR) | PagerDuty, Opsgenie, GoAlert, or similar incident management |
Charts and drill-down
- Trend charts appear when a live metric has at least two daily data points in the selected period.
- View breakdown opens a drill-down sheet for supported live metrics (contributing pull requests, workflow runs, security alerts, repositories, or branches).
- Recommended next step links to that same list. Metrics without a list link to the metric. Connect prompts open Integrations.
- Top actions and Correlated signals jump to the metric or module, and use the same links.
Use SDLC Insights to improve delivery pipelines, security posture, and platform cost. Do not use it to rank individual engineers.
Who sees what
All workspace members with Insights access can open SDLC Insights and most modules. Security & Risk Metrics and Financial & Operational Infrastructure are restricted to workspace admins.
SDLC Insights vs Leadership Dashboard
SDLC Insights is the detailed module catalog (34 metrics, drill-downs, integration unlock paths). The Leadership Dashboard is a portfolio roll-up for executives: Agentic readiness, delivery trends, and AI adoption at a glance. Use both when you need summary vs deep module analysis.