Kendis aims to make tracking of PI execution super simple for everyone. The challenge for RTEs and other program-level roles is enormous in terms of keeping track of what was planned, what has changed, and what caused the delay of a feature.

In this Kendis release, the following features are rolled out.

Details about each of these features are explained in the following sections.

With this new Kendis release, analytics are redesigned to bring key information to the fingertips of the users.

Analytics view is divided into the following sections

It's the same as older analytics, the only difference being the team and feature progress charts moved to the "Delivery by Teams" section.

This section focuses on the following key points

More details are available at the help portal.

The delivery by teams section in Analytics focuses on providing the progress by teams from multiple different dimensions including

More details are available at the help portal.
​

This section is the same as older analytics.

This section is focused on a single team at a time. It provides an overview for

More details are available at the help portal.
​

Often in the case of Jira sprints integrated to Kendis, there are differences in the load at Kendis sprint and in Jira. The main reason is some of the stories are in Jira/AzureDevOps sprints but they are not at Kendis.

With this new capability, you can run a comparison between Kendis sprint contents and Jira/AzureDevOps sprint.

The reason to start the sprint in Kendis is to set the baseline contents for each sprint at Kendis and provide information for tracking of changes and spill over contents.

This release is not yet available for Kendis Enterprise (Self-hosted) customers.

We are eagerly awaiting to bring some more cool features to the hands of our customers. For the short term roadmap, our teams are focusing on

For any feedback, reach out to us at support@kendis.io