The Sprint performance widget is in the new Engineering Performance dashboard. This feature works with monday dev's GitHub integration to track tickets within a sprint along with their corresponding Git status in GitHub. 

 

 

What is the Sprint performance widget?

The Sprint performance widget goes beyond basic status tracking by leveraging data visualization for a comprehensive sprint performance dashboard.

It will empower your development teams to proactively manage workflow, identify bottlenecks, and make data-driven decisions throughout the sprint cycle.

This feature provides real-time insights into the key performance metrics related to pull request handling during the development process.

What does it track?

The widget tracks the following metrics:

• Time to pull request (PR): Measures the time taken from when a task is moved to "in progress" to when a pull request is opened, helping to assess the speed of task initiation.
• Time to Code Review (CR): Captures the time elapsed from when a PR is opened to when the first code review event occurs, indicating the responsiveness of the review process.
• Time to Approval: Tracks the time between the first code review event and the moment the last approval is received, highlighting how long it takes for reviews and approvals to be completed.
• Time to Merge: Measures the time from the last approval to the actual merge of the PR, providing visibility into the efficiency of the merging process.
• Cycle Time: Represents the total time from task initiation ("in progress") to the final PR merge, offering a holistic view of the entire development cycle.

 

How does it work?

For each metric (Time to PR, Time to CR, Time to Approval, Time to Merge, and Cycle Time) in the Sprint performance widget, there are two tables that offer granular insights:

• Items Table: This table lists the items currently parked at a specific metric. For example, if a pull request has a review event but is waiting for approval, it will be parked in the "Time to Approval" metric.
• Item History Table: This table contains items that were once parked at a particular metric but have now moved to a more advanced phase in the process.

 

Each item includes the following fields:

• Item Name: The name of the corresponding task in monday dev
• PR Link: A direct link to the associated pull request
• SP: The effort estimate in story points (currently defaulting to the task SP column but will be adjustable in the future)
• Owner: The person responsible for the item
• Time in Phase: The time the item has spent in the current phase
• Phase: The current phase (available in the Items table)

These tables help track the flow of tasks through various stages of the development cycle, providing managers with a clear view of both ongoing and historical progress.

They are sorted by phase time, from higher to lower, making it easy to identify problematic items in every phase.

 

How to access the dashboard

To generate a Sprint performance widget, you'll first need to install the GitHub integration for your account, as GitHub is currently the only supported provider.

Once the integration is set up, you'll need to link pull requests (PRs) with items. To do this, simply include the item ID in either the body or title of the PR. This linking process ensures that the PR appears in the engineering dashboard, allowing you to track its progress.

 

To access the widget, click on the Performance button on the right side of the active sprint, as seen below:

 

This button will open a modal with these two widgets: the Sprint performance widget and the Burndown chart:

 

Both widgets will have the sprint context, so the dashboard metrics will be created only from the sprint tasks.

 

If you have any questions, please reach out to our team right here. We’re available 24/7 and happy to help.