Project management / Sample template
Sprint planning and commitment
Agree a sprint goal, check delivery capacity, and review the proposed commitment.
Read-only example. Adapt roles, fields, and checks to your organization before use. This preview does not create tasks or collect information.
- Process owner
- Product owner
- Frequency
- Configure after import
- Steps
- 10 steps, including approval
Workflow steps
- 1
Record scope and request details
Responsible role: Product coordinator
Confirm the scope, responsible contacts and planned date before starting. Agree a sprint goal, check delivery capacity, and review the proposed commitment.
- 2
Confirm owners, resources and work plan
Responsible role: Product coordinator
Prepare the work plan for sprint planning and commitment. Confirm resources, responsibilities and approved instructions before starting the domain activities.
- 3
Review backlog and acceptance criteria
Responsible role: Delivery lead
Review prioritized work and acceptance criteria. Record actual outcomes and evidence references. Keep this step open if required work cannot be completed; escalate exceptions to the responsible owner.
- 4
Confirm team delivery capacity
Responsible role: Delivery lead
Check team capacity and planned absences. Record actual outcomes and evidence references. Keep this step open if required work cannot be completed; escalate exceptions to the responsible owner.
- 5
Resolve dependencies and questions
Responsible role: Delivery lead
Identify dependencies and unresolved questions. Record actual outcomes and evidence references. Keep this step open if required work cannot be completed; escalate exceptions to the responsible owner.
- 6
Agree the sprint commitment
Responsible role: Delivery lead
Confirm the proposed scope with the delivery team. Record actual outcomes and evidence references. Keep this step open if required work cannot be completed; escalate exceptions to the responsible owner.
- 7
Record results and supporting evidence
Responsible role: Delivery lead
Record actual results and supporting references. Identify unresolved actions, responsible owners and target dates before requesting review.
- 8
Resolve exceptions and corrective actions
Responsible role: Delivery lead
Resolve required corrections before requesting sign-off. Document verification and any agreed non-blocking follow-up. Keep the process open when blocking issues remain.
- 9
Verify evidence and decision readiness
Responsible role: Product owner
Independently review the sprint planning and commitment record against the agreed scope. Return incomplete evidence for correction before making the approval decision.
- 10
Review results and approve next action
Responsible role: Product owner
Review the scope, checklist, evidence and unresolved actions. Approve only within your authority; request corrections for incomplete or unsupported submissions.