Jira Sprint Goal Writing and Backlog Item Selection Coaching
Craft a goal the team can believe in and test it.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Coach me in writing a sprint goal for Jira. Product and the current quarter's priority: [PRIORITY]. Candidate stories with sizes: [CANDIDATE_STORIES]. Team capacity and recent velocity: [CAPACITY_AND_VELOCITY]. Dependencies and risks: [DEPENDENCIES_AND_RISKS]. Write three possible sprint goals from different angles (a user outcome, a risk reduction, a learning goal). For each give the one-sentence goal, why it matters, which stories serve it and which do not, and how the team will know on the last day whether it was achieved. Recommend one with reasons. A goal is not a list of tickets; if the stories do not add up to one purpose, say so. Check the chosen goal against five tests: it is a single outcome, it can be demonstrated, it fits capacity, it has a clear owner, and it survives one unplanned absence. Select the stories the goal needs first, then fill remaining capacity, with arithmetic: with capacity of 26 points and a goal needing 18, 8 remain, and holding back 20 percent for the unexpected means planning about 21 in total. Write the goal in the form for the board header and as a two-sentence version for stakeholders. Where a feature depends on plan or configuration, tag it [VERIFY].
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.
See an example result (fictional data)
Invented inputs: capacity 26 points, three candidate goals. Goal A 'Customers can pay by card' needs 18 points of stories. Goal B 'Cut checkout errors by half' needs 12. Goal C 'Learn whether customers use saved addresses' needs 5 (a spike). Recommendation: Goal A with 18 points, plus Goal C at 5 is 23 points; leaving 3 as slack (11.5 percent of 26). Test of the goal: it can be demonstrated in the review, one owner, survives one absence. Board header text: 'Customers can pay by card (demo on the last day).'
Illustrative only, made-up data. Your results will differ and must be reviewed.