Retrospective

Tags: Flow

With the Retrospective report you can compare your teams’ metrics across specific time frames. Use the Retrospective report to look back on your teams’ trends and capture where they are succeeding and where they might need guidance. Learn more about Delivery module metrics.

Team managers and engineering leadership can:

  1. View how changes in workflow affect subsequent sprints and work periods

  2. Compare team metrics across sprints and teams

  3. Track key organizational metrics over time

  4. Use the Retrospective URL to save and share the retrospective report.

Note: You must configure delivery configurations to view the metrics in Retrospective. Learn more about delivery configurations.

What metrics does Retrospective compare?

At the top of the report, you will see the filters you selected when configuring the report. Under the filter,  you will see the filters for setting the report. You can adjust these filters as desired. Once your filters are set, you will see information about key metrics displayed as Trends over time, Workload distribution groupings, and key Tickets for review. 

Find the metrics dropdown at the right of the report. Use the metrics drop down to select which metrics you want to appear in your report. 

Tickets are included in the Retrospective report if they are completed in the selected time period. Only tickets that are in a Done status are included. Any tickets marked Cancelled in the delivery configuration are excluded from the retrospective report. 

Trends

The Trends area displays the change over time of key metrics of your teams and organizations. These metrics include tickets completed, velocity, medican cycle time, backflow rate, median queue time, and total jitter.

  1. The arrow captures the overall trend. If the arrow is green, then the trend is positive. If the arrow is orange, the trend can be improved. 

  2. The bar graph visualizes the metrics for each period being compared. The blue bar at the far right represents the primary date range. This is the current period’s date range that the other periods are being compared to The previous periods are represented by the grey bars. 

  3. Hover over a bar to view the details for that period. Click View Tickets to view the tickets for that period.  This will take you to the Ticket log.

  4. To view Sources of Jitter, click Show details under Total Jitter. Sources of Jitter shows the jitter, instances, and trends of jitter.

The arrow captures the overall trend. If the arrow is green, then the trend is positive. If the arrow is orange, the trend can be improved. 

The bar graph visualizes the metrics for each period being compared. The blue bar at the far right represents the primary date range. This is the current period’s date range that the other periods are being compared to The previous periods are represented by the grey bars. 

Hover over a bar to view the details for that period. Click View Tickets to view the tickets for that period.  This will take you to the Ticket log.

Workload distribution

The workload distribution shows counts and percentage breakdowns by issue type in the primary period. The primary period is represented by the blue bar in the histograms. 

Workload distribution includes tickets completed by issue, story points completed by issue type, and tickets completed by cycle time.

Tickets for review

Tickets for review captures the completed tickets in the primary period.  You may want to review these tickets during retrospectives with your team. For example, if you see an increase in Cycle time in the primary time period when conducting a retrospective, you can use this section to quickly identify the tickets that contributed to that increase, and have a data-based discussion with your team. 

back to top


If you need help, please email support@pluralsight.com for 24/7 assistance.