Run sprints and a Gantt
on the same plan.
The team works the sprint board and the backlog. The same tasks sit on a Gantt with their dates and links, so the delivery date still has a schedule behind it.
What you get
Sprints, epics and a backlog, without a second tool
Everything here works on the project's own tasks, so nobody copies work between a board and a schedule.
Sprints with a goal and dates
Name the sprint, write its goal, set its dates, pull work in from the backlog and start it. One sprint runs at a time in each project, so the board always shows the current one.
Close a sprint without losing work
Completing a sprint moves every task that is not done into the sprint you choose, or back to the backlog, so nothing is left behind on a closed board.
A backlog you can sort out
Every task not in a sprint, in one list. Group it by status, priority, assignee or epic, show the columns you need, and change priority in the row.
Epics across sprints
Collect related work under a coloured epic, put the epics in order, and keep an epic open across as many sprints as it takes.
A burndown for every sprint
Remaining tasks day by day against the ideal line, with the done and remaining counts, the pace so far and the finish it projects.
Sprint work stays on the schedule
A sprint task is an ordinary task, so it keeps its dates, links and place on the critical path. Filter the Gantt by sprint or epic, or move a selection into a sprint in one edit.
Sprints for the team, a schedule for the date
One set of tasks, read two ways
Most teams that run sprints still owe someone a date. When the board and the schedule are separate tools, the two drift apart within a week.
The sprint board shows the current sprint in status columns, with its goal and dates above it.
The Gantt shows the same tasks with their dependencies and the critical path, and filters them by sprint or epic.
The backlog holds every task that is not in a sprint yet, and the next sprint is filled from it.
Free, no account
Start from a task list you already have
Paste a list and see it scheduled, or take a ready-made plan as a spreadsheet, before you set up a single sprint.
Questions about sprints in Onplana
Which plan do I need?
Sprints, epics and the backlog are on the Professional plan and up, and the burndown is on the Professional plan and up. The Gantt with the critical path is on every plan, including Free, so a project can start as a schedule and add sprints when the team wants them.
Can one project have sprints and a Gantt at the same time?
Yes. A sprint is a set of the project's ordinary tasks, so the same task sits on the sprint board and on the Gantt with its dates, its links and its place on the critical path. Moving it between sprints does not move its dates, and moving its dates does not take it out of the sprint.
What does the burndown count?
Tasks. The ideal line runs from the number of tasks in the sprint down to zero across its dates, and the actual line drops as tasks are marked done. Above the chart sit the done and remaining counts, the pace so far and the finish date that pace projects.
What happens to unfinished work when a sprint ends?
When you complete a sprint, every task that is not done moves into the sprint you pick, or back to the backlog if you pick none. Done tasks stay with the sprint they were finished in.
Can more than one sprint run at once?
Not in one project. Starting a sprint while another is active is refused, so the board, the burndown and the backlog all agree on which sprint is current. Plan the next sprints ahead and start each when the last one closes.
Plan the sprint. Keep the date.
Start with the Gantt today, add sprints when the team wants them, and both read the same work.