Sprint carry-over map
Carry-over is work a team commits to in a sprint but doesn't finish, so it rolls into the next one. A little is normal. A lot means plans that don't hold and less room for new work every sprint. This map shows how much carry-over there is, and where it comes from.
- Done in the sprint it started: 1 sprint, no carry-over.
- Not finished, so it rolls into the next sprint, twice. Done in sprint 3: 3 sprints, 2 of them carried over.
Every item you load is drawn across the sprint calendar. Cycle time is counted in sprints touched: an item done in the sprint it started scores 1. Hatched segments are sprints the item was carried into.
Which columns?
id,title,type,category,start sprint,end sprint,status, in any order. The sample CSV shows the format.- Common export names work too: Work Item Type, Issue Type, Area Path, Component, State, Iteration Path, and Jira's repeated Sprint columns (first and last sprint are used).
- Done, Closed, Resolved and similar count as done. Removed or cancelled items are left out. Open items run to the latest sprint in the file.
This page reads a CSV. With the skill, Claude reads each item's sprint history straight from Azure DevOps or Jira, then builds this same map. It works with a CSV too.
- Download the zip. No need to unzip it.
- Add it to Claude: Customize → Skills → + → Create skill → Upload a skill. Code execution and file creation need to be on.
- Ask: “Build my sprint carry-over map from Azure DevOps”, “…from my Jira board”, or attach a CSV.
Live data needs a read-only token, and Claude must be allowed to reach Azure DevOps or Jira (Settings → Capabilities; an admin does this on Team and Enterprise plans). In Claude Code, unzip it into ~/.claude/skills/. The skill uses your token for that one run only and never saves or shows it.
sprint-carry-over-map.zip · 16 KB
Nothing to show yet
Drop a CSV from Azure DevOps or Jira above to map your own team's sprints. Or look around first with a made-up team's sample data.
What stands out
Sprint calendar
Hover or tap a bar for details. Faded end = still open in the current sprint.
Sprints to done, by type
Completed items only. Follows the “Group by” switch above.
Where it hurts: type × category
Average sprints to done (completed items), with item count. Darker = longer.
How much of each sprint is inherited work
Items active per sprint. A rising hatched share means the team starts each sprint with less room for new work.