1.3.10 – Introduction to DORA Metrics and Improvements in Cockpit and Check-ins

Improvements and New Features

Introduction to DORA Metrics

As part of our mission to provide more visibility and autonomy to teams, we are excited to announce the introduction of DORA Metrics in our metrics engine. These metrics are crucial for engineering, and we started with the implementation of Deploy Frequency, now available in the cockpit.

To facilitate the capture of your team’s deployments, we offer three configuration options:

  • Deploy via CI/CD
  • Deploy via Release Tag
  • Deploy via PR/MR

Our goal is to make this functionality as customizable as possible, adapting to your team’s specific needs.

New Cockpit Visualization

Alongside the new metrics, we have made several visual improvements to the cockpit to make information visualization more intuitive. Now, in addition to system-level artifact visualization, you can view team-specific artifacts. This allows for a more detailed analysis of the root causes of problems your team is facing.

Improvements in Daily and Weekly Check-ins

We have enhanced the logic for delay alerts to prioritize more important items, encouraging the team to finish started tasks before beginning new ones. This also reduces clutter in the delayed items section, showing only critical information. Remember, you can still view all delayed items by clicking the check-in button.


  • The parameter for work item types is now considered in check-ins, whether for delivery date alerts or for delivery issues/risks.
  • Performance improvements and minor bug fixes.

1.3.2 – Team Work Themes and Bug Fixes

Improvements and New Features

Visualization of Team Work Themes in the Cockpit

We harnessed the power of Large Language Models (LLMs) to group work items into themes. Now, you can quickly and intuitively view all the themes your teams are working on.


  • Adjusted tooltip formatting in the dashboard charts.
  • Fixed the help modal in the cockpit, which was not loading.
  • Fixed the getWorkItems function for WIP items, which was not retrieving items without updates.

1.3.0 – Cockpit, Dashboard, Company-level Artifacts, and More

Improvements and New Features

Kody cockpit

Enhanced Visibility for Leadership

We have added a new layer of visualization for leaders of multiple teams. Now, it’s possible to see whether your engineering team is performing well or poorly. Two new features achieve this.

Company-level Artifacts

In addition to team-level artifacts, we now have organization-level artifacts. These provide essential information about what is happening with your teams so you know which team or project needs more attention at any given moment. Some of the artifacts include:

  • Alert for teams where flow quality has dropped, indicating they are no longer following best engineering practices or the processes defined by the organization;
  • Alert for potential sprint delays (for teams using Scrum);
  • Alert for a drop in productivity (increase in lead time);
  • Alert for a decline in quality.

Cockpit Screen

This screen focuses on providing this visibility to leadership. Here, you can view the above artifacts and critical metrics at the organization and team levels.

Metrics Dashboard

Additional visual charts for all organization and team-level metrics are now available. You can now see a historical view of your teams.

Support for Private Channels on Slack

You can now add Kody to private Slack channels.


The Insights Screen is Public Again: In update 1.2.0 (multi-team), the insights screen was accidentally made private. It is now public again, and you can share it with your team.

1.2.0 – Support for Multiple Teams and Scrum

Improvements and New Features

Multiple Teams in a Single Organization

  • Simplified Management: Now you can register and manage multiple teams within the same organization through Kodus Teams.
  • Automatic Contextualization: Kody adjusts its responses based on the specific channel where the question was asked. For users with multiple teams, Kody will ask you to specify which team you want information about.

Enhancements in Scrum Support

  • New Team Artifacts:
    • Sprint overflow items
    • Items added after the sprint start
    • Monitoring of high time spent on blocked tasks
  • Artifact Customization: Option to enable or disable Scrum artifacts according to your team’s needs, avoiding irrelevant notifications.
  • Retrospective Check-in: Implemented a new automatic check-in that occurs at the sprint closure or upon a specific command.
  • Sprint Delay Alerts: Delay alerts are now synchronized with the sprint’s end date, providing greater accuracy in deadline management.

Improvement in Activity Notifications

  • Grouping of Activities with Incomplete Descriptions: All worked activities that have incomplete descriptions or gaps will be grouped and sent the following morning, allowing for quick corrections.


  • Adjustments in Discord: We fixed an issue with character size in check-ins that was causing errors on Discord.

1.1.0 – Kody 10 times smarter and addition of buttons in the daily check-in


  • We have developed a new architecture for Kody, enabling it to answer much more complex questions.
    • Ask about “which items are in WIP,” “What current team metrics are,” and “Which of our flows represents the biggest gap.”
  • New command buttons were added on Check-in Day to improve the visualization of task statuses and activity metrics.
    • View changelog shows the movements made on the board in the last 24 hours, categorized by team member.
    • View delivery status: this feature displays all items in WIP and indicates whether they are on schedule, in warning, or delayed

Bug Fixes

  • Solved the issue where the Metrics Tool was not working correctly, even with metrics available in the database.

1.0.29 – Improvements in daily check-in with the addition of lead time metric by item type


  • Now, Lead Time and Lead Time In WIP are also calculated considering the types of items on the board (Bug, Story, Feature – according to the types configured on your board);
  • We have also revamped the daily check-in now; it is more focused on the progress or delay of items and also on the quality of the team’s workflow;
  • We have started to record daily artifacts about the team’s flow; these artifacts will be used to improve Kody’s responses (implementation coming soon) and also its understanding of the team’s progress history;
  • And finally, we have updated the section that tracks the team’s ongoing activities. According to the team’s historical Lead Time, this section highlights activities that have already exceeded or are close to exceeding the deadline.