> tpl_del_004
Sprint/Iteration Planning and Commitment Pack
Agile engineering squad sprint planning model and capacity calculator balancing net developer availability, historical velocity baselines, story point sizing, sprint goal definition, technical-debt allocation, and formal squad commitment sign-off.
Squad sprint capacity calculator balancing net hours, velocity, tech debt reserves, and sprint goal commitments.
Important Tech Document Template & Operational Notice
TinyCTO.tv Tech Document Template Notice: This template is a general educational and operational starting point. It is not legal, tax, accounting, investment, procurement, regulatory, security or certification advice. Requirements vary by jurisdiction, organization, contract and risk. Review and adapt it with qualified professionals before relying on it.
Problem Solved
Engineering squads commit to unrealistic sprint workloads based on raw gross hours rather than net capacity, leading to chronic mid-sprint rollover, rushed untested code, technical-debt accumulation, and developer burnout.
When to Use
- •Conducting bi-weekly sprint planning ceremonies across cross-functional product delivery squads
- •Calculating true net team capacity after deducting holidays, PTO, on-call support duties, and meeting overhead
- •Reserving dedicated 20% capacity allocations for architectural refactoring, bug fixing, and technical debt paydown
When NOT to Use
- •For high-level multi-year product strategy and feature prioritization scoring (use TPL-PDS-005)
- •For macro enterprise project estimation and three-point PERT modeling (use TPL-PPM-010)
5 Template Sections & Structural Outline
Calculating effective engineering hours: deducting holidays, planned PTO, on-call support duty (20-30% deduction), and recurring ceremony overhead.
Analyzing the last 3 sprints: calculating rolling average velocity, standard deviation, and team focus factor (completed story points / available hours).
Enforcing a mandatory 20% capacity reservation for technical debt remediation, minor bug fixes, dependency upgrades, and operational chores.
Defining a single, outcome-oriented sprint goal providing cohesive focus (e.g. "Enable self-service password reset for iOS beta users").
Formal whole-team commitment vote (Fist of Five), identification of mid-sprint delivery risks, and agreement on mid-sprint scope renegotiation rules.
Completion Instructions
Independent Review Checklist
- All mandatory sections completed
- No secrets or passwords included
- Executive sponsor sign-off obtained
Sprint/Iteration Planning and Commitment Pack - Worked Case Study
Fictional Entity: Payments Checkout Squad Bi-Weekly Sprint Planning & Commitment Model
Real-world production case study demonstrating complete operational adoption for Payments Checkout Squad Bi-Weekly Sprint Planning & Commitment Model.
- •Calibrated net capacity across 8 engineers, discovering 32% of gross hours were consumed by on-call interrupts and meetings
- •Instituted mandatory 20% technical debt reserve, paying down 44 legacy checkout database query bottlenecks over 6 sprints
- •Increased sprint commitment completion reliability (Say/Do ratio) from 64% to 91% across two consecutive quarters
Frequently Asked Questions
Why should velocity be measured in story points rather than hours?
Hours measure individual effort and vary wildly based on seniority. Story points measure relative size, complexity, and uncertainty, creating an abstract team-level currency that remains stable regardless of who picks up the specific story.
How should mid-sprint scope changes be governed?
If an emergency critical request enters the sprint, the Product Owner and squad must apply the "Trade-In Rule": for every story point added, an equivalent number of story points must be removed from the sprint backlog to preserve capacity balance.
What is the "Say/Do Ratio" and why is it a vital health indicator?
The Say/Do ratio measures Committed Story Points versus Completed Story Points at sprint end. Mature high-performing squads maintain a consistent Say/Do ratio between 85% and 95%. Ratios consistently below 70% indicate systematic over-commitment or external interruptions.
Download Tech Document Pack
Auth RequiredDownload all blank templates, worked scenarios, and verification manifests in a single verified archive.
Authoritative Sources
- The Scrum Guide: The Definitive Guide to ScrumKen Schwaber and Jeff Sutherland • OFFICIAL REQUIREMENT
- Agile Estimating and Planning (Mike Cohn)Mountain Goat Software • OFFICIAL REQUIREMENT
- Principles of Product Development Flow (Donald G. Reinertsen)Celeritas Publishing • OFFICIAL REQUIREMENT