Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Develop communication and reporting strategy for Risk Management #151

Open
6 tasks
nicolebrennan opened this issue Feb 28, 2025 · 0 comments
Open
6 tasks
Assignees
Labels
documentation Improvements or additions to documentation product story

Comments

@nicolebrennan
Copy link

nicolebrennan commented Feb 28, 2025

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...

Preview Give feedback

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.
@nicolebrennan nicolebrennan moved this to triage in jemison Feb 28, 2025
@nicolebrennan nicolebrennan self-assigned this Feb 28, 2025
@nicolebrennan nicolebrennan added documentation Improvements or additions to documentation product labels Feb 28, 2025
@nicolebrennan nicolebrennan moved this from triage to backlog in jemison Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation product story
Projects
Status: backlog
Development

No branches or pull requests

1 participant