• ★ 5.0 on the Atlassian Marketplace (17 reviews)
• Free for teams up to 10 users
• 30-day free trial for any team size
• Scrum and Kanban boards
• Opens inside Jira Cloud, no setup

A scrum master’s Jira dashboard should answer three questions before every stand-up: are we on track for the sprint goal, what is blocked, and is the team overloaded? Jira’s built-in gadgets can answer each of these separately, but you end up stitching together a burndown, a filter results table and a two-dimensional statistics gadget. This page shows what a good scrum master dashboard contains, how to build one with native Jira gadgets, and where PM Overview saves you the setup.

What a scrum master dashboard needs to show

• Sprint progress: work completed versus committed, by day, so you see drift early instead of on the last day.
• Velocity trend: completed story points over the last 5 to 7 sprints, for realistic sprint planning.
• Blockers and aging work: issues stuck in one status longer than usual.
• Workload per person: how the sprint’s work is spread across the team.
• Average task completion time: how long an issue takes from “In Progress” to “Done”.
• Recent events: what changed since yesterday’s stand-up (new issues, status changes, scope added mid-sprint).

How to build it with native Jira gadgets

1. Go to Dashboards › Create dashboard and share it with your project.
2. Add the Sprint Burndown gadget for the active sprint.
3. Add a Filter Results gadget with a JQL filter such as sprint in openSprints() AND status = Blocked.
4. Add a Two Dimensional Filter Statistics gadget (Assignee × Status) to see workload.
5. Open the board’s Reports › Velocity Report for the velocity trend (this report is not a dashboard gadget in Jira Cloud, so it lives on a separate screen).

This works, but it has gaps: velocity and average completion time are not on the same screen, there is no alert when a sprint slips, and every new team means rebuilding the dashboard by hand.

The same dashboard in PM Overview

PM Overview is a Jira Cloud app that puts these views on one screen, ready after install:

• Sprint progress and velocity tracker on one page, so planning and tracking use the same numbers.
• Average task completion time per sprint, to spot process slowdowns.
• Allocation breakdown showing where the team’s time goes.
• Latest events feed for a faster stand-up.
• Notifications and alerts when KPIs move outside the range you set.

Using the dashboard in your scrum events

• Daily stand-up: open Latest events and the blocker list; skip the status round.
• Sprint planning: use the average of the last few sprints’ velocity, not the best sprint.
• Sprint review: share sprint progress and allocation with stakeholders.
• Retrospective: compare average completion time across sprints to find where work waits.

FAQ

Can I show the velocity chart on a Jira dashboard?

Not natively in Jira Cloud. The Velocity Report lives under the board’s Reports tab. Apps such as PM Overview add velocity to a dashboard view.

Is PM Overview free?

Yes for teams of up to 10 users, under the Atlassian Marketplace free tier for Cloud apps. Larger teams pay per user; see the Marketplace listing for current pricing.

Up and running in 2 minutes

1. Install PM Overview from the Atlassian Marketplace. It is free for up to 10 users, and every team size gets a 30-day trial.
2. Open your Jira project and click PM Overview in the project navigation (or under More).
3. Pick a board and sprint. The dashboard fills itself from your existing Jira data. No gadgets, JQL or spreadsheets to set up.

What teams say on the Atlassian Marketplace