[Syed.Atyab@Codeline.rihal.om] Sprint Capacity Calculator in a Snap

[CodelineAtyab]

🗓️ Sprint Capacity Calculator – User Story

As a Product Owner,
I want a shared “Sprint Capacity Calculator” Google Sheet so the Scrum team can quickly plug in each member’s available hours and instantly see the total Sprint capacity, ensuring we pull only the right amount of work into every Sprint.

---

🎯 Goals

• Centralised & real-time capacity planning
• Zero manual math – built-in formulas do the heavy lifting
• Data-driven Sprint Planning that prevents over-committing

---

✅ Acceptance Criteria

#	Requirement	Details / Examples
1	Input Fields	• Sprint length (working days) • Team-member names • Daily productive hours per member • Planned time-off (hours or days)
2	Auto-Calculations	• Total individual capacity • Overall team capacity • Live updates with built-in formulas
3	Capacity Alert	Conditional formatting (e.g., red cell) highlights when the sum of story estimates exceeds team capacity
4	Story-Point Conversion	Separate tab converts capacity to Story Points when team supplies average historical velocity (pts/hr) – ready for Planning Poker
5	Burn-Down Chart	Lightweight burn-down auto-updates as remaining hours are logged each Sprint day
6	Permissions	• All Scrum roles (PO, Dev Team, QA, Scrum Master) = view • Only Scrum Master = edit formulas (prevents accidental changes)
7	Traceability	• Template link stored in ClickUp Wiki • Sheet version-controlled in Git for continuous improvement
8	Definition of Done	• Demo during Sprint Review • At least 2 team members verify calculations match their manual estimates for the upcoming Sprint

---

🛠️ Deliverables

1. Google Sheet template with all features above
2. ClickUp Wiki entry containing the live link
3. Git commit that tracks the initial version of the template

---

🔒 Security & Access

• Google Workspace sharing:
  • Viewer – PO, Devs, QA
  • Editor (formulas & structure) – Scrum Master only

---

🗺️ Usage Flow

1. Scrum Master copies the template at Sprint planning start.
2. Team enters availability & time-off.
3. Sheet displays total capacity and warns if overloaded.
4. Optional: switch to Story-Points tab for Planning Poker.
5. Throughout the Sprint, team logs remaining hours → burn-down auto-updates.
6. Review outcomes and improvements during Sprint Review; commit any template tweaks to Git.