Software & Engineering Team Sankey Diagrams
Sankey templates for software teams: cloud costs, engineer time, API errors, pull requests, CI pipelines, vulnerabilities, cloud migration and roadmap delivery. Figures are illustrative.
Software & Engineering Team Sankey Diagrams in this category
- Cloud Cost Allocation Sankey Diagram: Services to Teams — Follow a monthly cloud bill from the services that generate it to the teams that own it and the environments it runs in. Replace the sample figures with your own billing export.
- Engineering Time Allocation Sankey Diagram: Team Capacity — Show where a sprint's engineer-days go: from teams to feature work, bug fixes, tech debt, meetings and on-call, then to planned and unplanned work. Replace the sample days with your own.
- API Request Outcomes Sankey Diagram: Endpoints to Errors — Trace API requests from endpoint to status class to the cause of each error. See which endpoints produce failures and why, then replace the sample counts with your own logs.
- Pull Request Review Flow Sankey Diagram: Size to Merge — See how pull requests move from size to first review outcome to merge, rework or abandonment. Replace the sample counts with your own repository data to find where review stalls.
- Cloud Migration Strategy Sankey Diagram: Apps to Status — Map an application portfolio from business area to migration strategy (rehost, replatform, refactor, repurchase, retire, retain) to status. Replace the sample counts with your inventory.
- Vulnerability Remediation Sankey Diagram: Scan to Fix — Follow security findings from the scan that found them to their severity and to the outcome: fixed in SLA, fixed late, accepted, false positive or open. Replace the sample counts with your own.
- Roadmap Delivery Sankey Diagram: Planned vs Shipped — Compare what a quarter's roadmap promised with what shipped, was carried over or was cut, including work added mid-quarter. Replace the sample counts with your own roadmap items.
- CI Pipeline Outcomes Sankey Diagram: Trigger to Failure Cause — Trace pipeline runs from trigger to result and the cause of each failure: flaky tests, real regressions, config and environment. Replace the sample counts with your CI history.