Castor plans and tracks sprints for one scrum team: capacity planning from rolling velocity and availability, sprint closeout with rollover tracking, a daily standup runner, and velocity metrics. You enter planned and completed points per sprint; every metric is computed from that history.

• Everything you enter is stored only in this browser, on this device. No server holds a copy, and nobody else can see your data.
• That also means the browser is the only copy: clearing site data, browser resets, or a lost device delete your history. Exported backup files are your durability — see the backup routine below.
• A different browser or device starts empty. To move, export a backup and import it there.

On first open, Castor asks for the team basics. Everything can be changed later in Settings.

1. Team name — identifies your team, including in export files.
2. Roster with skill weights — each member gets a weight (1.0 = baseline) used in the team-availability calculation; a senior who delivers more can sit above 1.0, a new joiner below.
3. Cadence — sprints per PI and default sprint length, matching your ART's calendar. PI labels are free text, so use your own convention.
4. Tracker links (optional) — base URLs for your wiki and issue tracker. When set, sprints and rolled issues link out; when empty, the link buttons stay hidden.

Then create your first sprint from the Sprints tab. Capacity recommendations appear once a few completed sprints exist — the first sprints are data entry, not forecasts.

• Export: Settings → Data → Export → Full backup (JSON). Save the file somewhere durable (a drive folder, not the same machine's downloads).
• When: after every sprint closeout at minimum. Castor shows a banner when the last backup is more than two weeks old.
• Restore: Settings → Data → Import, pick a full-backup file. Restoring replaces what is in the browser with the file's contents.
• Program share (Export → Program share) is a sanitized file for program-level aggregation — numbers only, no notes, roster, or issue numbers. It is not a backup and cannot be restored. Hand it to whoever runs the program view, which rolls several teams' shares into one cross-team picture.

Refreshing the page loads the latest version. Stored data is migrated automatically — no action needed on your side.