At a glance
To ensure effective risk management, we need clear a communication and reporting strategy that outlines how risk related updates will be shared with stakeholders. This includes definiing the frequency, format, and responsible parties for the risk reporting.
Acceptance Criteria
- Define key stakeholders for risk reporting
- Establish reporting frequency
- Determine reporting format / Identify tools or platforms for risk reporting (written reports? Github? Slack?)
- Define escalation procedures for high priority risks
- Validate thee final strategy with stakeholders
Risk reports should include updates on new risks, mitigation process, outstanding issues, any shift in roadmap/timeline
Scenario:
### then...
- [ ] Identify key stakeholders and level of detail of the report
- [ ] Determine frequencies of the reporting: critical risks, low risks
- [ ] Establish reporting format and standardize content
- [ ] Define escalation procedures
- [ ] Ensure comms aligns with security policies
- [ ] Validate and finalize strategy
Shepherd
- Product shepherd: Nicole Brennan
- Engineering shepherd:
Background
Security Considerations
Required per CM-4.
Process checklist
If there's UI...
At a glance
To ensure effective risk management, we need clear a communication and reporting strategy that outlines how risk related updates will be shared with stakeholders. This includes definiing the frequency, format, and responsible parties for the risk reporting.
Acceptance Criteria
Risk reports should include updates on new risks, mitigation process, outstanding issues, any shift in roadmap/timeline
Scenario:
Shepherd
Background
Security Considerations
Required per CM-4.
Process checklist
If there's UI...