💰Investment
View the effort breakdown across work item types and investment across epics to ensure they are aligned to business objectives.
The Investment Screen provides comprehensive analysis of team efforts across five main sections: Work Item, Epic, Product and Allocation, Delivery and Hygiene.
Work Item | Epic | Product and Allocation | Delivery | Hygiene|
Sections:
Work Item
This area tracks "volume of work items or story points per sprint and type" to assess team capacity.
Key features include filtering by work item type (available as a filter in the Work Item page), sprint-level drilldown capabilities, and hygiene filters for identifying missing data like assignees or story points.

Filter on work item types: Click on any work item type to filter the graph data for only that type. The available types will be based on the items created in your Jira project and board.

Sprint-level drilldown: Click on a particular sprint bar to view detailed fields of each Jira work items within that sprint.
Filter to identify missing hygiene: You can apply additional filters such as "Missing Epics," "Missing Assignee," and "Missing Story Points" (by clicking on the corresponding buttons) to identify work items with missing hygiene and ensure they are updated for proper tracking.

Work Item Age
When you drill down into a sprint's work items, you'll see the Work Item Age column (refer screenshot above), which shows how long each item has been in progress from creation to completion.
Work Item Age = Completion Date − Creation Date
Example:
Creation Date: August 1, 2024
Completion Date: August 5, 2024
Work Item Age: 4 days
Why It Matters
Team Efficiency: Lower work item age indicates faster issue resolution and better workflow efficiency. Higher age may signal bottlenecks or delays needing investigation.
Customer Satisfaction: Faster resolution times directly impact customer satisfaction, especially for customer-facing work.
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 Work Item section, you can drill down into items 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.


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 : Work Items/Story Points completed before the sprint closes.
Spillover : Work Items/Story Points not completed by the time the sprint closes.
Planned : Work Items/Story Points created before the sprint starts.
Unplanned : Work Items/Story Points created after the sprint starts.
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) × 100What 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) × 100What 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.
Average Completed
This measures the percentage of all work items initiated during the sprint that were successfully finished by sprint end.
Formula:
(Work Items Completed / Total Work Items Started in Sprint) × 100What it means:
A high Average Completed (>80%) indicates strong execution discipline and suggests the team finishes what it starts.
A low Average Completed (<80%) may reveal work-in-progress buildup, incomplete handoffs, or scope creep on individual items, signaling a need to focus on closure over initiation.
🧠 Why Both Metrics Matter
When used together, Say-Do Ratio, Delivery Rate, and Average Completed provide a fuller picture of sprint health:
If all three metrics are high, the team is likely performing well: sticking to plans, completing committed work, and finishing what it starts.
If Delivery Rate and Average Completed are high but Say-Do Ratio is low, the team is completing work effectively but not sticking to the original plan (possible unplanned work absorbed mid-sprint).
If all three are low, the team may be overcommitting, facing blockers, or struggling with execution discipline—all areas needing investigation.
If Say-Do Ratio is high but Delivery Rate and Average Completed are low, it might indicate too much ad-hoc work was started but not finished, suggesting a focus problem.
If Say-Do Ratio and Delivery Rate are high but Average Completed is low, work is getting done but items are being left incomplete, signaling a closure or handoff issue.
Use these insights to improve sprint planning, manage expectations, and identify areas where the team may need support or process adjustments.
The Hygiene Tab: Your Data Quality Dashboard:
The Hygiene tab acts as a real-time inventory of data gaps across your project. It surfaces five categories of incompleteness:

No Assignee: Tickets without owners introduce planning ambiguity.
No Story Points: Unestimated work makes capacity planning unreliable.
No Epic Link: Orphaned tickets obscure your strategic initiatives.
No Allocation: Missing allocation mappings prevent accurate cost tracking.
No Product: Unmapped product fields hide resource distribution across your portfolio.
Rather than overwhelming you with a raw list, Hygiene starts with summary counts. You see at a glance how many tickets need attention in each category, then drill into specific work items to fix them where they matter most.
Filters:
In each of the sections, there are certain filters that can be applied to reflect only the relevant data:
Projects : Refers to Jira Projects. You can select upto 5 projects at a time.
Sprints (all screens) : Use this filter to display data based on specific sprints. Up to 30 can be selected, defaulting to the latest 5.
Assignees (only for Work Item, Epic, and Delivery sections) : To filter out data for the Assignees of Jira tickets.
Tickets/Story Points (all screens): Choose to view the data as either the count of tickets or the sum of story points.
Duration 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 support@hivel.ai.
Last updated