website logo
Sign upLogin
⌘K
πŸš€ Getting started
Introduction
Echoes fundamentals
Understanding Echoes data
Developer guide
Configuration guides
βš™οΈ CONFIGURATION
Outcomes
Initiatives
Members
Teams
πŸ”Œ INTEGRATIONS
Source code managers
Issue trackers
Incident management
Compatibility matrix
πŸ“Š REPORTS
Organization health
DORA metrics
πŸ€– API
Introduction
Authentication
Releases
Incidents
Efforts
Teams
πŸ”” NOTIFICATIONS
Email report
Slack notifications
πŸ‘€ ACCOUNT
Users & Roles
Single sign-on
Linking identities
Billing
πŸ₯· ADVANCED
Echoes IP addresses
Scoped publishing
Changelog
Docs powered byΒ archbeeΒ 
12min

Organization health

Purpose

The organization health report provides a synthetic evaluation of a team's context across different axes. It aims to answer the questions: do the teams have the what they need to succeed? It helps quickly identify the teams doing well and who may be able to share their learnings, and the team who might be needing support.

Organization health report
Organization health report

All data in this table is compared against the organization's average, the color intensity indicating the outliers (the values which most significantly depart from the organization's norm).

The report can also show you variation and highlight whether your management actions are having an impact, positive or not, on the teams.

Date and variation settings
Date and variation settings
Organization health report showing a 3 months variation
Organization health report showing a 3 months variation

Context evaluation

Team composition

The first group of columns covers team composition, with the following metrics:

  • Tenure: the average time in years for which the current members of the team have participated in that team.
  • Churn: the percentage of members having left the team over the past year.

They are automatically computed from your organization's data, and don't require any particular action other than keeping the teams definitions up-to-date.

Software delivery performance

The second group of columns covers software delivery performance, with the DORA metrics:

  • ο»ΏLead timeο»Ώ
  • ο»ΏDeployment frequencyο»Ώ

  • ο»ΏMean time to recoveryο»Ώ
  • ο»ΏChange failure rateο»Ώ

Their prerequisites are explained in each individual metric page.

Impediments

The last group of columns covers impediments declared by the teams, categorized as:

  • Dependencies: the percentage of changes made difficult by external dependencies (e.g., blocked by another change or another team).
  • Knowledge gap: the percentage of changes made difficult by a lack of available knowledge (e.g., documentation, code familiarity, particular technological stack).
  • Technical debt: the percentage of changes made difficult by technical debt (e.g., high coupling, lack of tests).
  • Unclear requirements: the percentage of changes made difficult by a lack of clear requirements.

They are computed from the echoes/impediments labels being applied to GitHub pull requests and GitLab merge requests.

Impediments labels are an experimental feature being progressively rolled-out. Please reach out if you would like us to enable it for your organization.

Updated 26 Sep 2022
Did this page help you?
Yes
No
UP NEXT
DORA metrics
Docs powered byΒ archbeeΒ 
TABLE OF CONTENTS
Purpose
Context evaluation
Team composition
Software delivery performance
Impediments