Delivery Cycle Analysis (professional edition)

The Delivery section is designed to help product and engineering managers identify bottlenecks, assess the performance of their delivery cycles and gain valuable insights into the software development life cycle (SDLC).

Drill Down into Delivery Data

One of the key features of the Delivery section is the ability to drill down into data surrounding a delivery cycle, such as a sprint. This feature allows you to view historical data and current issue statuses, which can be used to spot bottlenecks.

When used as part of a Sprint retrospective, users can view which items were completed during the sprint and the status of all items at the end of the sprint. This feature can be particularly useful for identifying process bottlenecks, which can be spotted using the Development Time and Issue Duration breakdowns. Additionally, the Investment priorities or Delivery Areas are published in this location, which shows the type of work that was completed during the selected time period.

Now let's take a closer look at the components of the Delivery section:

Delivery Areas: Understanding the relationship between work assigned and time spent on those assignments allows leaders to ensure their team is focusing on the right things. The first chart shows the number/type of issues resolved and the second chart presents the amount of time spent on each issue type. Users can select to view the data by Sprint, Months or Weeks.

Delivery Duration: This section pulls data from the code repository and /or project management tool and presents an interactive chart that is ideal to spot process shortcomings or bottlenecks. It's recommended to view the longest bar(s) in the chart to understand where branches, reviews, and issues spend the most time in the process. If the stages showing the longest duration are designated waiting stages, this may be acceptable, but it also shows where time can be taken out of the process. If the longest duration stages are critical parts of the development and deployment cycle, such as time coding, time testing, time deploying, it may show that one or more teams are struggling with either the volume or complexity of the work requested. Looking for abnormalities: increases in stage duration across various time periods will show bottlenecks.

Sprint Completion and Details: This feature shows the amount of prioritized work that was completed during the sprint. A completion rate that is less than 60% is indicative of an overloaded sprint or delivery issues such as unplanned work. However, if the sprint completion % is consistently lower than 60%, this is an issue with assigning too much work or not breaking down that work into smaller bite-sized development projects. The listing of items in the sprint allows users to view each issue and identify which items took the most amount of effort to complete.

In summary, the Delivery section of Treno's engineering analytics platform provides valuable insights into your SDLC's performance and can help you identify areas that require attention or improvement. By following the analysis steps outlined above, you'll be able to use this section to gain valuable insights and optimize your development processes.