Configuring Retrospective Processes
Retrospectives have configurable, customizable processes, made of up steps, to allow a right sized retrospective based severity, type or teams involved in an incident.
A retrospective process is a series of steps that will be applied to an incident and guide responders through a retrospective. Rootly provides a default retrospective process with generalized steps that will work for many use cases. No configuration is required, the default steps will be applied to all incidents.
For more opinionated incident practices, retrospective processes can be created, customized and applied to incidents meeting specific requirements. The ability to scale retrospective processes based on the severity, team or type of incident allows programs to right size their retrospective process and support responders regardless of what kind of incident occurs.
The following incident attributes can be used to apply custom processes:
Processes can also be configured to be required or auto skipped based upon the same incident attributes.
- Required retrospective processes are not able to be skipped by responders.
- Auto Skipped processes are not skipped by default, but have the option to be reinstated at responder discretion.
Note: by default, retrospective processes have the option to be skipped on a per incident basis by responders via the button at the bottom of the retrospective tab.
SEV1 incident example
Apply a more rigorous process that requires the following steps:
- Gather information
- Hold retrospective meeting
- Peer review of generated document
- Publish retrospective document
Each of these steps have automatically: assigned step owners based upon incident role, relative due dates and owner reminders.
SEV3 incident example
Apply a flexible, light weight process with the following optional, skippable steps:
- information gathering
- self facilitated team retrospective meeting