Use Sprint Goals in Jira
Write the sprint goal as the outcome guiding scope decisions and record it with the sprint. A collection of issue titles does not explain why the team chose that work.
Step-by-step guide
Check access and scope
You need a Scrum workflow and permission to edit or manage the sprint. Discuss the goal with the delivery team before communicating it as a commitment.
Write the sprint outcome
Describe the outcome the sprint should demonstrate.
Review scope contribution
Check that planned issues contribute directly or explain exceptions.
- Worked example: A useful goal is Enable internal administrators to recover expired invitations. A bug fix unrelated to that outcome should have an explicit reason for consuming the same sprint capacity.
Record the sprint goal
Record the goal in the sprint editing controls available to your board. For a company-managed space, open Backlog and choose Edit sprint from its more menu; the sprint name, goal and eligible dates can be edited there.
Evaluate scope changes
Use the goal when evaluating additions or deferrals.
Review the outcome
Review the outcome alongside incomplete work at sprint end.
Verify the result
Team members can explain the sprint outcome and why the selected scope contributes to it.
Common mistakes
Check the handoff edge case
Treating every new request as an automatic addition undermines the goal. Review capacity and the intended outcome before accepting it.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.