Skip to main content

Retrospective

Retrospective involves recording a journal of Cadence Goal and Deliverables at a regular cadence. This regular review and metrics collection allows for the collection of sentiments and statistical analysis. This documentation captures key insights, successes, and challenges encountered during the Cadence, providing a comprehensive record for evaluating performance and identifying areas for improvement. By maintaining this journal, the team can track progress over time, analyze trends, and make informed decisions to enhance future delivery cycles.

Purpose​

The purpose of Retrospective is to record a journal of the Process Script progress metrics for review and statistics. These metrics include objective measurements, as well as individual sentiments.

Cadence​

It occurs once per cycle in the hours before the cadence ends.

Time​

Retrospective should be scheduled for 45 minutes.

People​

The Product Owner and full Delivery Team are required at Retrospective. The Process Steward and any invested Coordinators can also be invited.

Input​

Artifact: Cadence Plan
Artifact: Task Board
Artifact: Previous Retrospective Document

Output​

Artifact: Retrospective Document

Process​

If present, the Process Steward facilitates Retrospective. Otherwise, any other member may facilitate. The facilitator leads the discussion and recording of answers to the following topics as the Retrospective Document:

• The Cadence Goal and its achievement
• What happenings of the Cadence went “Well” and “Not Well”
• Updates on Action Items
• Newly proposed Action Items
• Updates on Experiments
• Newly proposed Experiments

Action Items and Experiments​

An Action Item is a powerful tool for specifically assigning an individual to a small task. Action Items are expressed by naming a person who is to perform the action and then succinctly stating what action that person should take. Action Items may also include a due date. Process Script recommends adding Action Items to the upcoming Candence’s Task Board.

Experiments are a method for Process Teams to test new approaches or modifications to improve team performance and productivity. These experiments are implemented on a small scale, allowing teams to evaluate their impact and effectiveness without disrupting the overall workflow. At the cadence of Retrospective, the team evaluates results of the experiment and makes a decision on whether to adopt, adjust, or discard the experiment for future iterations.