retro

To run a structured retrospective, use pre-defined templates that guide the team through sprint reviews and project postmortems. The process automatically pulls contextual information like recent commits to ensure key learnings are captured and actionable items are identified.

The best way to conduct a post-incident review is using structured templates that guide incident analysis. This approach ensures all key aspects of the incident are covered, contextual data is gathered, and learnings are captured for future reference.

Yes, you can automatically capture knowledge during a postmortem. The process optionally integrates key learnings and contextual information into a knowledge base, ensuring valuable retrospective insights are persisted for future reference.

Yes, the retrospective template automatically pulls relevant context such as recent commits and merged PRs. This automatically gathered contextual information helps the team accurately review project progress and incident details during the session.

To start a post-incident review session, initiate the review using the incident argument. This triggers the structured template and contextual information gathering needed to guide the team through the postmortem process.

You should use a structured template for a project retrospective after critical incidents, sprint reviews, or project postmortems. It streamlines knowledge capture and ensures valuable learnings are systematically gathered and acted upon.