Skip to content

Develop communication and reporting strategy for Risk Management #151

@nicolebrennan

Description

@nicolebrennan

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
  • Has a clear story statement
  • Can reasonably be done in a few days (otherwise, split this up!)
  • Shepherds have been identified
  • UX youexes all the things
  • Design designs all the things
  • Engineering engineers all the things
  • Meets acceptance criteria
  • Meets QASP conditions
  • Presented in a review
  • Includes screenshots or references to artifacts
  • Tagged with the sprint where it was finished
  • Archived

If there's UI...

  • Screen reader - Listen to the experience with a screen reader extension, ensure the information presented in order
  • Keyboard navigation - Run through acceptance criteria with keyboard tabs, ensure it works.
  • Text scaling - Adjust viewport to 1280 pixels wide and zoom to 200%, ensure everything renders as expected. Document 400% zoom issues with USWDS if appropriate.

Metadata

Metadata

Assignees

Labels

Type

No type
No fields configured for issues without a type.

Projects

Status

backlog

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions