📦 Product Backlog
🎯 Themes
Strategic initiatives that group related Epics together.
🗺️ Epics
Large bodies of work under a Theme. Progress tracks linked stories.
📋 Backlog Items
Sprint Hub
Sprint Setup
Sprint Progress
Burn-down Chart
Velocity History
Last 5 completed sprints. Archive a sprint to record velocity.
💡 Looking to save or load a sprint? Head to in the sidebar.
📚 Sprint Library
💾 Save / Load Sprint File
Snapshots include sprint setup, backlog, daily entries, impediments, review, retrospective, and velocity.
📁 Quick Saves (in-browser)
Up to 5 slots — stored in this browser only. Good for switching between sprints on the same device.
Sprint Planning
Topic 1 — Why is this Sprint valuable?
The Product Owner proposes value; the Scrum Team collaborates to define the Sprint Goal.
Topic 2 — What can be Done this Sprint?
Capacity: — ptsDevelopers select from the Product Backlog based on capacity and Definition of Done.
Topic 3 — How will the chosen work get done?
Click "Tasks" on a backlog item to break it into sub-tasks.
Select a backlog item above to add tasks.
Daily Scrum
Team
⏱️ 15-Min Timer
Impediments
Sprint Review
Attendees
Key stakeholders collaborate on what to do next.
What was accomplished?
Items from Sprint Planning — check off completed work.
What changed in the environment?
Product Backlog Adjustments
Sprint Retrospective
✅ What Went Well
🔄 To Improve
🎯 Action Items
🎨 AI Story Generator
The Story Generator analyses your UI screenshots using Claude AI. Because this app runs entirely in your browser with no backend server, it connects to the Anthropic API directly — which means you need your own API key.
Your key is stored only in your browser's localStorage and is never sent anywhere except directly to Anthropic.
Get a free API key at console.anthropic.com →
No key saved.
📤 Upload & Configure
⚙️ Options
📝 Generated Stories
Sprint Poker
📋 Pick from Backlog
✏️ Or Enter Manually
📖 Fibonacci Reference
We use the Fibonacci sequence for sprint points to estimate duration. Points represent effort, complexity, and uncertainty — not hours exactly.
| Points | Duration | Description |
|---|---|---|
| 0 | 0 mins | No effort required, or no business value delivered (e.g. a behavioural change from a stand-up). |
| 1 | 30 min – 1 hr | Extra Small — Developers understand the requirement fully and consider it an easy change. |
| 2 | 1 – 2 hrs | Small — A little thought and effort required, but the developer has done this before and is confident. |
| 3 | 2 – 4 hrs | Average — Done this before, know what's needed, may have a few extra steps. No research needed. |
| 5 | 4 – 8 hrs | Large — Complex or unfamiliar work. May need team assistance. Generally the largest item in a weekly sprint. |
| 8 | 8 – 16 hrs | Extra Large — Will take time and research; a few assumptions that may add risk to completion. |
| 13 | 16 – 24 hrs | ⚠️ Warning — Complex with lots of unknowns. Needs to be managed carefully by leads. |
| 21 | 24 – 40 hrs | 🚨 Hazard — Too complex for a weekly sprint. Needs refinement by the dev lead; more risk, assumptions, and dependencies involved. |
| 40 | 40 – 80 hrs | 🔴 Danger — Must be broken up. Not enough information to begin, plan, or complete this work. |
Ceremony Timer
Timeboxes from the 2020 Scrum Guide, scaled to your sprint duration.
Select a ceremony above
Custom Timer
Scrum Reference
Three Pillars of Empiricism
Transparency
The emergent process and work must be visible to those performing and receiving the work.
Inspection
Artifacts and progress toward goals must be inspected frequently to detect undesirable variances.
Adaptation
If a process deviates outside acceptable limits, it must be adjusted as soon as possible.
Five Scrum Values
When these values are embodied by the Scrum Team, the empirical pillars come to life building trust.
Accountabilities
| Role | Accountable For |
|---|---|
| Scrum Master | Establishing Scrum as defined in the Guide; team effectiveness; coaching self-management; facilitating events; removing impediments |
| Product Owner | Maximising product value; Product Backlog management; communicating the Product Goal; ordering backlog items |
| Developers | Creating the Sprint Backlog; adhering to Definition of Done; adapting plan daily toward Sprint Goal; holding each other accountable |
Events & Timeboxes
| Event | Purpose | 1-wk | 2-wk | 4-wk |
|---|---|---|---|---|
| Sprint | Container for all other events | 1 wk | 2 wks | 4 wks |
| Sprint Planning | Lay out work; define Sprint Goal | 2h | 4h | 8h |
| Daily Scrum | Inspect progress; adapt Sprint Backlog | 15 min | 15 min | 15 min |
| Sprint Review | Inspect increment; determine adaptations | 1h | 2h | 4h |
| Sprint Retrospective | Improve quality and effectiveness | 45 min | 90 min | 3h |
Artifacts & Commitments
| Artifact | Commitment | Description |
|---|---|---|
| Product Backlog | Product Goal | Emergent, ordered list of what is needed to improve the product |
| Sprint Backlog | Sprint Goal | Sprint Goal + selected backlog items + plan for delivering the Increment |
| Increment | Definition of Done | Concrete stepping stone toward the Product Goal; must be usable |
Skills Self-Assessment
Scrum Master Skills MatrixRate yourself on each skill. Saved locally.
⚡ Priority Board
Rank tasks by Impact and Effort. Items from Sprint Planning are imported automatically — add standalone tasks here too.
➕ Add Task
📖 Priority Guide
Impact / Effort Matrix
📋 Ranked List
🧠 Quiz Me
Answer 10 questions a week to keep your badge active. Badges expire after 7 days.
📊 Your Stats
Ready for your weekly check-in? 10 random questions across Scrum, Agile & Product Ownership.