Predictions at the epic and issue level are based on a machine learning model that accounts for every single field within the issue and how it has impacted completion over time, including summary and description information. Predictions at the initiative level are based on the last completion date of epics within that initiative.
The goal of Velma Insights is to proactively detect work that may contain risks as early as possible. Velma triggers and guides important project conversations. The project status and projected finish dates will help you prioritize what information to look at first. The Risks, Progress, Changes, and other insight drill-downs will give you as much context as possible about how work has completed in the past and how it's trending in the present and future. This information can then be weaved together to help you ask the right questions and make informed decisions.
You can turn on insights by clicking "Show Insights" on the "Options" menu in the upper right-hand corner. This will reveal blue columns on the screen. These are usually interspersed with the grey columns (your team's inputs), in an order that makes it easy to compare and understand what's going on. If you want to modify the order, please let our team know and we can configure it for you!
The insights are automated predictions based on historical work progress in the project as well as the team, current updates on the project, and remaining work to be completed. By default, all companies will have insights run once a week to correspond with when they'd like to send out a report on the status of projects.
The current available predictions are:
This blue column on the right shows a projected Red/Yellow/Green status corresponding to whether a project is On Track, At Risk, or Off-Track respectively. Often, this can be compared to manually reported statuses in order to gut-check whether a project may need additional help.
This is based on the projected finish date (see field details below) of the project compared to the due date or the end of the quarter as well as potential risks (see details in the "Potential Risks" section below) that may put the project behind.
At the issue level (stories, bugs, tasks, etc), the projected finish date takes into account all the fields within that issue and compares that against all issues that have completed in the past. The model finds trends in previous issues, whether that be a particular assignee or a particular phrase mentioned in the description, to predict roughly how long it believes this issue will take to complete. It also takes into account how many days have already been spent on it to adjust its predictions.
Even if the issue is not assigned or story pointed, it will factor in the description of the issue, team, project, creators, and anything that may impact the trend of work over time.
At the epic level, it takes into account all the predictions of issues within that epic along with approximately how the epic has completed so far. For example, it takes into account the percentage of time it thinks each developer is spending on the epic compared to other issues the developer is assigned, and it takes into account approximately how many developers are assigned to the epic in total. It uses all these measures to then predict a final projected finish date for the epic.
At the initiative level, it just uses the last projected finish date of any epic within it.
These are potential risks that may impact the completion of the epic or body of work. It is not a definite that each risk will cause a problem within the project. However, they are helpful signals to use to ask the right questions and make sure the team is getting support where they need. A running list of all available risks as well as risks under development can be found here.
This tracks all changes that were made to particular fields in the initiative, epic, or issue over a selected span of time. At the bottom of the "Filter", you can select when you want to see changes.
Then, you can click into each field to see what the specific change was. If you're having trouble seeing the "Changes" column, make sure Velma Insights are on by going to Options > Show Insights. Then, make sure you scroll all the way to the right in the dashboard, because it currently appears at the last column in Blue.