friction-retrospective

You can analyze delivery friction by scanning delivery artefacts for friction log entries to extract and categorize events. The analysis detects recurring patterns based on predefined categories and frequency thresholds, producing retrospective reports that identify systemic improvement opportunities.

Friction analysis in continuous improvement workflows is the process of scanning post-delivery artefacts to extract and categorize friction events. It identifies recurring patterns and themes in friction types to highlight systemic improvement opportunities for your delivery process.

Generate a retrospective report by parsing delivery artefacts to extract friction log entries and classify friction types. Based on predefined categories and frequency thresholds, the system flags high-signal events and recurring patterns for potential promotion to durable memory like conventions or decisions.

Yes, you can detect missing context or tool failure patterns from sprint artefacts. The pattern detection feature identifies themes and frequencies in friction types by scanning captured friction logs, highlighting if multiple stories consistently struggled with unclear requirements or tool failures.

Yes, predefined categories and frequency thresholds are required for friction classification. The retrospective analysis applies to post-delivery analysis by parsing artefact reports and classifying friction types based on these predefined categories and frequency thresholds to detect recurring patterns.

Run a post-delivery analysis on friction logs after a series of development sprints. Activating this analysis reviews all captured friction logs to highlight recurring patterns, suggesting needs like better upfront requirement definition or establishing new conventions for continuous improvement workflows.