SupportBook a demoTry it free

Sprint kickoff template set for Jira

Start every sprint the same way: the kickoff epic, its work items and the scope checklist, created in one step on the first day.

1 epic · 4 work items · 1 subtask · On request

Read: How to run a sprint kickoff with Jira templates

Illustration of the Sprint kickoff template set in the app, with sample data.

The structure

What it creates

Each run creates an epic for the sprint, four work items under it and a subtask for sharing the goal. The scope work item carries a checklist, so the conversation that starts the sprint covers the same ground every time.

Most teams rebuild this epic by hand every two weeks. With the set, the scrum master types the sprint number once and the whole kickoff is ready.

  • Sprint $sprint kickoffEpic
    • Confirm sprint scopeA checklist: review the backlog, agree on scope, check capacity, flag risks.Story
    • Update the board filtersPoint the board and its quick filters at the new sprint.Task
    • Book the sprint reviewSend the invite for the last day of the sprint.Task
    • Share the sprint goalPost the goal where the team and stakeholders will see it.Task
    • Post the goal in the team channelSubtask

The line under each item is a suggested scope. Write your own in each work item's description.

What fills in

Variables

Variables fill in what changes from run to run. They work in text fields, such as the summary and description. A user variable fills in a person field, such as Assignee.

Variables in the Sprint kickoff template set
VariableWhat it fills inExample
$sprintThe sprint number in the epic summary; a text variable you add24
$teamLeadEach work item's Assignee; a user variable you addDana Ortiz

Both are custom variables. The app asks for them when you apply the set on the sprint’s first day.

When it runs

How to run it

Use one way, or more than one. Each way creates the same structure.

  1. 01

    On request

    Apply it from the app when the work starts.

    The app asks for any variables, so each run carries its own details.

  2. 02

    From Jira Automation

    Call the app's API from a rule.

    Use this when an event in Jira, such as a field change, should start the work.

  3. 03

    On a schedule

    Every two weeks with a custom CRON schedule.

    Save the variable values with the schedule. Teams with fixed sprint dates use this.

Who it's for

Scrum masters and team leads who start a sprint every one or two weeks and want the kickoff to cover the same steps.

It suits teams where kickoff steps get skipped when the sprint starts on a busy day.

When not to use it

If your team doesn’t run sprints, use the weekly review set instead.

Sprint planning itself happens in your board. The set covers the work around it, not the planning.

Sprint kickoff: common questions

Does the sprint number go up by itself?

No. $sprint is a text variable, so you type the number when you apply the set.

Can we add a retro work item?

Yes. Add a work item to the set for the retrospective at the end of the sprint, and every kickoff will include it.

Is there a step-by-step guide?

Yes. Our sprint kickoff guide walks through building the set, adding variables and checking the first run.

Other template sets that teams use alongside this one.

Browse the template library
Goals for sprint $sprint
Draft the sprint goal
Agree on owners
Set due dates
+1 more
GuideEngineering

The same goal-setting steps, owners and due dates for each sprint.

1 work item, 4 checklist items · On request

See the template set
Release $version
Freeze the release branch
Run the release tests
Update the version in the docs
+6 more
GuideEngineering

Your release steps as a checklist, ready for each version.

1 work item, 9 checklist items · On request

See the template set
Weekly review, $todayEvery Friday
Review open work
Update priorities
Share the notes
ExampleOperations

Review open work with your team at the same time each week.

1 work item, 3 subtasks · Every Friday

See the template set
Part of AppsDelivered

Repeatable work, delivered.

Building Jira apps since 2017.

AppsDelivered CommentsReuse your team's replies.See AppsDelivered CommentsAppsDelivered FeedsTurn new posts into work items.See AppsDelivered Feeds