💰Investment

View the effort breakdown across issue types and investment across epics to ensure they are aligned to business objectives.

The Investment Screen provides a detailed view of your team's efforts as tracked in Jira issues. It is divided into four sections, each offering specific insights into different aspects of your team's work:

Issue | Epic | Product and Allocation | Delivery

Sections:

Issue

• Gain visibility into the volume of issues or story points per sprint and issue type. This helps you assess whether your team is working within capacity or if there is room for improvement

1. Filter on issuetypes: Click on any issue type to filter the graph data to only that issue type. The available issue types will be based on the issues created in your Jira project and board.

1. Sprint-level drilldown: Click on a particular sprint to view detailed fields of each Jira issue within that sprint.

1. Filter to identify missing hygiene: You can apply additional filters such as "Missing Epics," "Missing Assignee," and "Missing Story Points" to identify issues with missing hygiene and ensure they are updated for proper tracking.

All the sections in Investment follow a similar above behaviour of filtering on issuetype, sprints and arriving at the drilldown.

Epic

• This section provides visibility into the volume of tickets and story points at both the Epic and sprint levels. It helps you understand the efforts spent on specific Epics within each sprint.

• Similar to the Issue section, you can drill down into issues by clicking on a sprint and filter by selecting a particular Epic from the available options.

Product and Allocation

Hivel's Products and Allocation sections helps you see where your team's efforts are going. It shows how resources are split across your products through Jira tickets. By mapping your custom Jira labels in Hivel, you can get a clear picture of this distribution and make smarter investment decisions.

Products section

Allocation section

For more information on how to set up this functionality, please refer to this article.

Delivery

The Delivery Accuracy graphs offer insights into the completion rate of planned efforts within a sprint and highlight any unplanned items that were addressed, as well as any delays encountered.

The delivery bar chart data is categorized into two main sections: Completed and Spillover. Each section is further divided into Planned and Unplanned.

• Completed : Issues/Story Points completed before the sprint closes.

• Spillover : Issues/Story Points not completed by the time the sprint closes.

• Planned : Issues/Story Points created before the sprint starts.

• Unplanned : Issues/Story Points created after the sprint starts.

Delivery Trend

Delivery Trend

The Delivery Trend chart helps you track and evaluate your team’s sprint execution by combining two key metrics:

1. Say-Do Ratio

This measures the accuracy of sprint planning by comparing what was committed at the start of the sprint to what was actually delivered.

• Formula: (Work Delivered from Sprint Start / Work Committed at Sprint Start) × 100

• What it means:

  • A high Say-Do Ratio (>100%) could indicate significant ad-hoc work is being added and completed, possibly reducing focus on planned items.

  • A low Say-Do Ratio (<100%) suggests that the team is overcommitting or facing blockers, pointing to potential areas where expectations or planning should be adjusted.

---

2. Delivery Rate

This measures how much of the total work taken up during the sprint - both planned and ad-hoc - was actually delivered.

• Formula: (Total Work Delivered / Total Work Taken Up in Sprint) × 100

• What it means:

  • Always shown as a percentage out of 100%.

  • A high Delivery Rate indicates effective throughput, regardless of how work entered the sprint.

  • A low Delivery Rate may signal capacity issues, scope creep, or blockers mid-sprint.

---

🧠 Why Both Metrics Matter

When used together, Say-Do Ratio and Delivery Rate provide a fuller picture of sprint health:

• If both metrics are high, the team is likely performing well and adapting effectively.

• If Delivery Rate is high but Say-Do Ratio is low, the team is completing work but not sticking to the original plan (possible unplanned work).

• If both are low, the team may be overcommitting or facing blockers that need investigation.

• If Say-Do Ratio is high but Delivery Rate is low, it might indicate too much ad-hoc work was started but not completed.

Use these insights to improve sprint planning, manage expectations, and identify areas where the team may need support or process adjustments.

---

Filters:

In each of the sections, there are certain filters that can be applied to reflect only the relevant data:

• Boards/Sub boards : Boards refer to Jira Projects and Sub boards refer to the boards inside a Jira project. You can select only one Board at a time, but you can select any number of Sub boards within that Board. All subsequent filters will apply on the selected Boards/Sub board filter.

• Sprints (only for Issue, Epic, and Delivery sections) : Use this filter to display data based on specific sprints. By default, the latest 5 sprints will be selected.

• Assignees (only for Issue, Epic, and Delivery sections) : To filter out data for the Assignees of Jira tickets.

• Tickets/Story Points : Choose to view the data as either the count of tickets or the sum of story points.

• Date filter (only for Product and Allocation sections) : Filter the Product and Allocation data for a specified time period.

For more information or assistance, please contact our support team at [email protected].