How to Use Health Reports in Cubyts?

Introduction

This guide explains how to use Health Reports in the Cubyts platform to analyze execution health and identify risks early. Using an EPIC or Portfolio Health Report as an example, this walkthrough shows how to interpret health scores, prioritize high-impact fixes, analyze flags, and track trends for continuous improvement.
 Once you understand one health report, you can apply the same approach across portfolios, EPICs, sprints, and repositories.

Prerequisites

• Access to a Cubyts workspace

• Permission to view health reports

• Connected SDLC tools (for meaningful health and flag insights)

Step-by-Step Guide

Step 1: Open the Health Analysis Landing View

1. Navigate to Health Reports within your Cubyts workspace.

2. The Health Analysis Landing View displays a selector at the top of the page.

From this selector, you can choose the type of health report you want to view.

Step 2: Select a Health Report Type

• Use the selector to choose a report type such as:
  
  

  • Portfolio health/EPIC health

  • Sprint health

  • Repository health
    
    

• Based on your selection, Cubyts lists the relevant artifacts along with their health scores.
  
  

At the top of the view, you’ll also see a distribution of artifacts across health categories such as:

• Excellent

• Good

• Warning

• Bad

• Poor
  
  

This distribution helps you quickly identify which artifacts require attention.

Step 3: Review the Overall Health Score

• Select an artifact (for example, an EPIC or portfolio) to open its detailed health report.

• The first section displays the overall health score.

• This score is calculated using a proprietary algorithm that considers:

  • Flags raised on the artifact

  • Flags on its dependent artifacts

This provides a consolidated view of execution health at that level.

Step 4: Identify High-Impact Fixes

• Below the health score, review High-Impact Fixes.

• These represent the most critical flags that, if resolved, will significantly improve the overall health score.

This section helps teams focus on what matters most instead of addressing issues in isolation.

Step 5: Analyze Key Execution Metrics

• On the right-hand side of the report, Cubyts displays key execution metrics such as:

  • Deadline progress

  • Delivery progress

  • Average cycle time
    
    

These metrics provide additional delivery context alongside governance insights.

Step 6: Deep Dive into Related Execution Artifacts

Below the summary, Cubyts lists all execution artifacts associated with the selected portfolio or EPIC, including:

• Work items

• Branches

• Pull requests

• Audit logs for merged PRs

• Audit deviations for ongoing artifacts

• Contributor and reviewer logs

• Peer-level details

Each item acts as a deep-dive entry point.
For example, selecting merge PR audit logs allows you to review all merge-related activity for the chosen EPIC or portfolio.

This supports continuous, data-driven retrospective analysis instead of point-in-time reviews.

Step 7: Review Flags Across Active Sprints

• The report includes a status-wise distribution of flags across all active sprints where related work items are being executed.

• Flags are grouped by execution status such as:

  • Backlog

  • In progress

  • Done
    (based on the status configuration in your planning tool)

This view highlights where issues are accumulating and which execution stages require immediate attention.

Step 8: Use the Flag Monitor

• The Flag Monitor allows you to select up to six critical flags to track closely.

• These selected flags define your personal focus areas and remain visible throughout the report.

This ensures important risks are always in view without scanning through all flags.

Step 9: Analyze Flag Trends

• The Flag Trend section shows how flags have evolved over time.

• Flags are grouped by categories such as:

  • Planning

  • Requirements

  • Development

  • Quality

  • Security

  • Compliance

  • Deployment

  • Operations
    
    

This bird’s-eye view helps identify improvement areas and emerging concerns.

Step 10: Review Workflow and Sprint Trends

• Workflow Overview shows how flags are distributed across execution stages like:

  • Backlog

  • Active sprints

  • Planned sprints

  • Completed sprints
    
    

• Each stage displays:

  • Work item count

  • Flag count

  • Overall quality indicator
    
    

• Trend Across Sprints compares flags across the last four sprints, helping teams understand whether issues are:

  • Reducing

  • Persisting

  • Increasing
    
    

Consistency Across All Health Reports

While the artifact may change (portfolio, EPIC, sprint, or repository), the structure, sections, and interpretation pattern remain the same across all health reports in Cubyts.

Once you understand how to read one health report, you can confidently analyze all others.

Conclusion

Health Reports in Cubyts provide consistent, actionable insights across every level of delivery. By combining health scores, high-impact fixes, execution metrics, flags, and trends, teams gain continuous visibility into risks and execution quality—enabling proactive governance and ongoing improvement.

Video link: https://www.loom.com/share/cbb5ca0169b54144953fd66905e8a263