when sprint completed, i want to send report to stockholders

[Murali Ganesh Chitrothu]

How many Items Done, Item id: description
what items moving to Backlog or next sprint
% of completing 

[Dave Mathijs · Accepted solution]

Hi @Murali Ganesh Chitrothu welcome to the Atlassian Community Forums.

Jira Cloud offers a variety of reports for scrum spaces (see below).

You can use any of these reports to provide feedback to the stakeholders.

Reports for scrum spaces

Burndown Chart

Applies to: Sprints

Tracks the total work remaining, and spaces the likelihood of achieving the sprint goal.

This helps your team manage its progress and respond accordingly.

Burnup Chart

Applies to: Sprints

Provides a visual representation of a sprint's scope, as well as its remaining work.

This helps your team stay on track.

Sprint Report

Applies to: Sprints

Shows the work completed or pushed back to the backlog in each sprint.

This helps you determine if your team is overcommitting or if there is scope creep.

Control Chart

Applies to: Spaces, versions, or sprints

Shows the cycle time for your app, version, or sprint.

This helps you identify whether data from the current process can be used to determine future performance.

Cumulative Flow Diagram

Applies to: Any period of time

Shows the statuses of work items over time.

This helps you identify potential bottlenecks that need to be investigated.

Epic Report

Applies to: Epics

Shows the progress towards completing an epic over time.

This helps you manage your team's progress by tracking the remaining incomplete and unestimated work.

Epic Burndown

Applies to: Epics

Similar to the Epic Report, but optimized for scrum teams that work in sprints. Tracks the projected number of sprints required to complete the epic.

This helps you monitor whether the epic will release on time, so you can take action if work is falling behind.

Release Burndown

Applies to: Versions

Similar to the Version Report, but optimized for scrum teams that work in sprints.

Tracks the projected release date for a version. This helps you monitor whether the version will release on time, so you can take action if work is falling behind.

Velocity Chart

Applies to: Sprints

Tracks the amount of work completed from sprint to sprint.

This helps you determine your team's velocity, and estimate the work your team can realistically achieve in future sprints.

Version Report

Applies to: Versions

Tracks the projected release date for a version.

This helps you monitor whether the version will release on time, so you can take action if work is falling behind.

[Alexey Pavlenko _App Developer_]

Hi @Murali Ganesh Chitrothu ,

My app Multi-team Scrum Metrics & Retrospectives has all the info you are looking for.

The screenshots below are with X-Axis = Story Points setup, but it can be changed to Issue Count. In this case, you will get 

• Done = Completed Scope,
• Item id: description = tickets included in Completed Scope
• what items moving to Backlog or next sprint = Uncompleted Scope

• % of completing = % out of Final Scope

Analysis of 1 period:

Analysis of all periods, average:

You can take screenshots and send them to stakeholders, or I can implement a snapshot feature that automatically emails snapshots to stakeholders if you’re ready to buy the paid version.

Best regards,
Alexey

[Iryna Komarnitska_SaaSJet_]

Hi @Murali Ganesh Chitrothu ,

Jira already offers several sprint metrics reports, and those have been recommended above.

As an alternative, you might consider the sprint report available in Time in Status by SaaSJet (built by my team).

The app includes two one-page sprint report options with the key metrics:

• Active sprint report (to track progress during the sprint)

• Completed sprint report (to review results after the sprint)

It’s a compact, informative way to share sprint performance with stakeholders.

Documentation: Sprint Report in Jira's Time in Status App for Comprehensive Sprint Analysis

Hope you find it useful!

[Danut M _StonikByte_]

Hi @Murali Ganesh Chitrothu,

Welcome to the Atlassian Community.

Jira provides solid reports for sprint tracking that you and your team can use to visualize sprint progress.

However, for stakeholders, a concise one-page sprint report containing all the key metrics is often more effective to share at the end of a sprint.

My recommendation is to create a Jira dashboard or a Confluence page that brings together all the necessary gadgets or macros to present the metrics you want to highlight.

Both Jira and Confluence offer useful built-in gadgets and macros you can use to build your sprint reporting dashboard or Conflunece page, such as the Sprint Burndown gadget, Sprint Health gadget, and Two-Dimensional Filter Statistics gadget.

And if you need more gadgets/macros, you can search for an app on Atlassian Marketplace, like, for example, our Great Gadgets app which offer all you need for building effective dashboards and Confluence pages: sprint burndown/burnup chart, release burndown burnup, team velocity, pivot tables, epic progress, and more.

And they are capable to also track the sub-tasks, in case your team sets estimates on sub-tasks.    

Have also a look over this article: https://community.atlassian.com/forums/App-Central-articles/9-gadgets-for-a-powerful-Scrum-dashboard-in-Jira/ba-p/1683063

Danut.