Jira Dashboard for Product Management

(Image 1)

• The Task Breakdown Chart (Image 1) offers a dynamic visual representation of your Kanban or Sprint board (Image 2) directly within PM Overview. It's automatically prefilled with data from your boards, providing users with an at-a-glance view of how their tasks are allocated across the board.
• Users have the flexibility to interact with this chart by easily removing or hiding categories simply by clicking on them. This feature empowers users to customize their view for enhanced task management.

(Image 2)

Notifications & Alerts

• PM Overview includes a Notification Section (Image 1) that keeps users informed about critical project metrics and early warning signs.

(Image 1)

• It provides alerts about missing story point estimations, sprint completion percentages, tasks added during sprints, sprint velocity compared to the average velocity, and more!
• If you're working in a "Scrum" Board, you'll also see the current sprint duration in the title. 

Latest Events

• The Latest Event Section displays real-time activity related to tasks. Users can track and act to changes, comments, and updates made by team members, ensuring everyone is up-to-date on task progress.

Coming soon: capabilities to customize alerts and choose which alerts to show/hide.

KPI - Story point completion

• The Story Point Completion Chart provides insights into the breakdown of story points across different stages, including "Todo", "In Progress", and "Completed". 
• Users can effectively assess how well their team is meeting story point commitments and gain visibility into trends. This empowers them to identify potential bottlenecks and step in where needed to ensure project success.

• The Velocity Chart provides a comprehensive overview of your project's performance. It showcases essential metrics, including the average velocity, total commitment, and completed story points per sprint or timeframe, along with a historical record of all previous sprints.
• What makes this chart particularly powerful is its high level of customization. Users have the flexibility to filter sprints into "commitment" and "completed" categories and exclude specific sprints for in-depth analysis using easy-to-use settings.
• Furthermore, this chart is entirely adaptable, allowing users to change the data source and incorporate a custom timeframe for a more tailored analysis. (Refer to Section 10 for more info)

Allocation breakdown (stakeholder reporting)

• The Allocation Breakdown Chart is a powerful tool for stakeholder reporting and future planning. It empowers users to gain a deep understanding of resource allocation by visually representing how tasks are distributed based on labels or epics.
• Users can filter the chart to focus on completed and allocated tasks, with values and percentages calculated from story points. This enables users to gain valuable insights into resource allocation, such as how resources are allocated to areas like bug fixes, new features, specific milestones (e.g., Milestone X, Milestone Y), or reducing technical debt.
• There is a high degree of customization. Users can tailor it to showcase allocation breakdowns on weekly, monthly, or yearly scales, making it an invaluable tool for both stakeholder reporting and future planning.

Average task completion time

• Users can analyze task completion times based on various parameters, such as task type (e.g., tasks, bugs, stories) and timeframes. The second chart categories the allocation chart on Labels and epics.

• There are in-depth customization options for timeframes, sprints, data sources, and units (hours or days) via the side panel settings - refer to Section 10 for more info.

• The Planning Section offers a centralized view of all tickets organized into sprints or custom timeframes. Users can easily prioritize tasks by dragging and dropping them, and you can also quickly access and manage open tickets by clicking on the ticket ID. 

• The completed tasks section lists all completed tasks within the current sprint, previous sprint, or custom timeframes. Users can review task details and assess sprint progress. It is also helpful to easily reflect on previous sprints.

• The Product Goals & Initiatives Section within PM Overview serves as a versatile workspace for managing product goals and enhancing stakeholder engagement. Users can seamlessly add tasks that are not directly linked to Jira tickets, allowing for a broader scope of project management.
• What sets this section apart is its adaptability. Users have the flexibility to customize titles, aligning them with specific project needs and objectives. This makes it a dynamic space for tailoring your product management approach.
• The Product Goals & Initiatives Section is particularly well-suited for several purposes. It can be used as a personal to-do list, enabling users to keep track of tasks and objectives outside the Jira ticketing system. Additionally, it provides an excellent platform for collecting stakeholder feedback and input before formalizing Jira tickets, ensuring that project priorities are aligned with stakeholder expectations.

Board Customization settings:

• The Board Customization Settings offer users a high degree of flexibility in tailoring their PM Overview experience to their specific needs. These settings can be accessed from the top right corner of the interface.
  • Users can switch between different boards and sprints directly from this menu, which will automatically prefill the PM Overview dashboard based on the selected board. For Kanban boards, the workflow follows the Kanban methodology.
• Additionally, users can select the "View settings" button to open a sidebar settings configuration panel. This panel provides a range of customization options to fine-tune the dashboard according to individual preferences and project requirements.
• Configuration options available in this panel include:
  1. Custom timeframe: this option will update the following sections:
     • 4. Story point completion chart
     • 5. Velocity chart
     • 6. Allocation breakdown chart
     • 7. Task completion time charts
     • 8. Completed tasks section 
  2. Task source timeframe: Users can select from options like:
     • Backlog (Default for Kanban)
     • Sprint (Default for Scrum)
     • Or both (Offering extra customizability in reporting.)
  3. Task Completion time charts
     • Start time
       • Choose between the columns on your board
     • End time
       • Choose between the columns on your board
     • Tracking period
       • Show chart & data in Hours or Days
  4. Display/hide KPIs: Here, users have the flexibility to hide or show charts and graphs to optimize screen real estate and focus on the most relevant information for their workflow.

How to access the PM Overview plugin in Jira

A) In a Scrum project

1. Open your Scrum project in Jira.

2. In the top navigation bar you’ll either see PM Overview directly or under the More (…) menu.

3. Click PM Overview to launch the Jira dashboard.

B) In a Kanban project

1. Open your Kanban board in Jira.

2. Look for PM Overview in the board toolbar— if it’s not shown, click More (…) and pick PM Overview.

3. The Jira dashboard will open (its full feature set shines in Scrum, but it’s available on both Kanban and Scrum).