Key takeaways
- In Jira, a planning board is a Scrum board: its backlog is where you rank issues, estimate them and move them into sprints.
- Creating one takes six steps: create the board, pick the project or filter, set estimation, map columns, fill the backlog, start a sprint.
- Kanban boards can have a backlog too, for teams that plan continuously instead of in sprints.
- For several teams and longer horizons, Jira Plans (Premium and Enterprise) adds a timeline across boards.
- A Jira board plans issues, not people's days; ActivityTimeline shows whether the sprint fits each person's hours, time off included. You can try it free for 30 days.
Sprint planning goes wrong in a familiar way. The backlog looks ranked, the sprint looks full, and on day three you find out that one developer is on holiday and another has twice the work of everyone else.
A Jira planning board fixes the first half of that: one place to rank, estimate and commit to work. Here's how to set one up, step by step, and how to check the second half, whether the people can actually do it.
What is a planning board in Jira?
A planning board is a Jira board with a backlog, usually a Scrum board. The backlog lists every issue not yet in a sprint, in priority order; you estimate issues there and drag them into the next sprint. The board itself then tracks the sprint's progress through columns.
How do you create a planning board in Jira?
- Create the board. In a company-managed project, open the board menu and choose Create board, then Scrum. In a team-managed project, turn on Sprints in the project's Features instead; the project already has its board.
- Choose the source. Pick Board from an existing project for one project, or Board from an existing saved filter for several projects.
- Set estimation. In Board settings → Estimation, choose story points or original time estimate, and how time is tracked.
- Map the columns. In Board settings → Columns, make sure every status in the workflow sits in a column.
- Fill and rank the backlog. Open Backlog, create or import issues, drag them into priority order and estimate the top ones.
- Plan and start the sprint. Click Create sprint, drag issues from the backlog into it until it matches your team's usual velocity, set the dates and click Start sprint.
Scrum board or Kanban board for planning?
How do you plan beyond one board?
A board plans one team's next sprint. For releases across several teams, Jira Plans (included in Jira Premium and Enterprise) puts issues from several boards and projects on one timeline, with dependencies and releases. Teams on the Standard plan usually use releases (Fix Versions) and the project timeline for that.
Does the sprint fit your team's capacity?
Velocity tells you how many points the team usually finishes. It doesn't know that Maria is off Thursday and Friday, that there's a public holiday on Monday, or that Alex already has 30 hours on another project. That's where most sprint plans break.
ActivityTimeline reads the same Jira issues and lays them out per person, per day:
- Each team member is a row on a timeline; you see the sprint's issues on the days each person will work on them.
- Each day shows how full it is: green when fully planned, red when overloaded, blue when out of office.
- Time off, holidays and imported calendar meetings reduce the hours available.
- Sprints and releases appear as milestones on the same timeline.
Honest limit: ActivityTimeline plans in hours, so if your team only uses story points, you'll need hour estimates for the issues you schedule. More on that in capacity planning in Jira.
FAQ
How do I create a sprint planning board in Jira?
Create a Scrum board from your project or a saved filter, set estimation in Board settings, rank and estimate the backlog, then create a sprint, drag issues into it and start it. In team-managed projects, turn on the Sprints feature instead of creating a board.
Can a Kanban board have a backlog in Jira?
Yes. In Board settings → Columns, turn on the Kanban backlog. Issues then wait in a separate backlog view instead of the first column, which makes continuous planning easier.
What is the difference between a Jira board and Jira Plans?
A board plans and tracks one team's work, usually sprint by sprint. Jira Plans, in Premium and Enterprise, combines several boards and projects on one timeline for longer-range planning, dependencies and releases.
How do I know if a sprint is overloaded?
Compare the sprint's estimate to the team's average velocity, then check each person's hours against their time off. Jira does the first; a capacity tool such as ActivityTimeline shows the second, per person and per day.
If your sprints look full in Jira but break on day three, check them against real capacity. Try ActivityTimeline free for 30 days. Start the trial
