Plan your sprints and track progress with burndown

For Scrum teams, Subtask keeps the backlog and planned, active and completed sprints on one screen. See the task count and total story points for each sprint, track progress with a burndown chart throughout the sprint, and return unfinished tasks to the backlog in one step when it ends.

Create a free account Try without signing up

Unlimited users · No per-user fees · No installation required

Subtask sprint backlog: active sprint, story points and issue detail

Create a workspace with a sprint model

When creating a workspace, choose a work model that supports sprints. The backlog, sprints and sprint reports are automatically enabled, and a sprint selector appears on task forms. A software team using sprints and an operations team using simple kanban can work side by side in the same company.

From backlog to sprint

The workspace's main view lists the backlog and planned, active and completed sprints in separate sections. Each section shows the task count and total story points, so you can see immediately whether you are exceeding the team's capacity as you fill the sprint.

  1. Create a sprint with a name, start date and end date.
  2. Move backlog tasks into the sprint; enter estimates in story points.
  3. Start the sprint. Move tasks forward on the board or in the list during the sprint.
  4. When the sprint ends, decide what to do with unfinished tasks: return them to the backlog or mark them as completed.

Burndown chart and sprint report

Every sprint's report tab includes a burndown chart. Chart data is calculated automatically each day; see day by day whether the team is ahead of or behind the sprint goal.

The sprint summary includes:

Below the report is a list of tasks completed in the sprint; you can open this screen directly in your sprint review (retrospective) meeting.

Story points, time estimates and worklogs

Tasks have both story point and time estimate fields; fill in whichever your team uses. Record actual time spent with worklogs. This gives you data to answer 'how much did our estimates differ from the time we spent?'.

Sprint meetings in Subtask

Create meetings in the calendar for sprint planning, daily meetings and retrospectives, and add participants. Open an agenda from the meeting and turn decisions into action items with owners and due dates. Improvements identified in the retrospective stay visible for the next sprint.

For development teams: GitHub and AI

When you connect a GitHub repository to a workspace, PRs and commits containing the task key appear in task details. You can also send a task to an AI agent using Solve with AI, then review and merge the resulting PR. When the PR is merged, the task automatically moves to the status you selected.

Frequently asked questions

Can Subtask be used as a free Scrum tool?
Yes. The backlog, sprints, story points and burndown chart are free, with no user limit.
What happens to unfinished tasks when a sprint ends?
When ending the sprint, you choose: unfinished tasks return to the backlog or are marked as completed.
How is the burndown chart calculated?
Remaining work is calculated automatically each day during the sprint and added to the chart in the sprint report.
Can I migrate my sprint and story point data from Jira?
Story points, estimates, statuses, assignees and epic/subtask links from the Jira CSV export are imported. Sprint records are not imported; you recreate sprints in Subtask. See the Jira migration guide.
Are email notifications sent when a sprint starts?
Task assignments have in-app notifications and an email flow. To share the sprint schedule with your team, we recommend creating sprint meetings in the calendar.

Bring your team together in one place

Get started with Subtask for free, invite your team and create your first task in minutes. The price does not change with your user count.

Create a free account
We use cookies to improve user experience and analyze website traffic. By clicking “Accept“, you agree to our website's cookie use as described in our Cookie Policy.
error_outline Name, surname, email and message field must be valid!
error_outline Email field must be valid!
error_outline Unauthorized transaction!