Follow projects execution
Echoes leverages all the data it collects about your teams' activity to help you drive your projects to success.
A project in Echoes is called an initiative. An initiative in Echoes gets its own label created in your integration, such that work items can easily be added to its scope.
The initiatives report gives a quick overview of all projects your teams' are participating in:
This view gives you for each initiative:
- A computed status (more on that below).
- The number of identified risks on the initiative.
- The number of completed tasks over the total number of tasks. This counter is a combination of tickets across all of your integrations (e.g., GitHub issues, JIRA issues, Linear tickets, ...).
- The change in tasks over the period under examination.
- A synthetic burn-up chart to show the variation in scope and completion.
Clicking on any row of this table brings you to a detailed view of the project:
Echoes computes a status for your initiatives. This status is an aggregation of all currently idenfiied risks that may directly of indirectly impact the success of the initiative.
Echoes leverages its insights to determine the status of an initiative. Any open insight that either applies to the initiative directly (e.g., when the forecated completion date exceeds the desired target) or to any of its major contributing teams (e.g., the team's delivery pace is degrading) is considered as a potential risk for the initiative.
Dismissing initiative insights
The status of initiatives is deduced from currently identified risk. Those risks can be dismissed just like any other insights when you judge them irrelevant, for example in case of additional context knowledge that would mitigate their severity. A dismissed risk will stop contributing to the overall initiative status.
Each risk identified for an initiative contribute to the overall initiative status based on its severity.
Severity | Score | Comment |
|---|---|---|
Low | 1 | All risks have a low severity by default. |
Medium | 5 | Example: the initiative appears to be slightly delayed and is at risk of meeting its target date. |
High | 10 | Example: the initiative is very unlikely to be completed by its target date. |
The aggregated status of the initiative is determined by the sum of its associated risks' severities.
Status | Severity score | Comment |
|---|---|---|
On track | < 5 | Some risks may be identified, but their amount and severities are not sufficient to impact the global status. |
At risk | >= 5 | It takes a single medium severity risk, or 5 low severity risks, to make an initiative "at risk". |
Off track | >= 10 | It takes a single high severity risk, or a combination of low and medium severity risks, to make an initiative "off track". |