USTC: Production Launch Plan DUP - #4003

[mariahkannenberg]

As a project team, in order to have a successful launch and mitigate risk, we need to get a launch plan in place

Pre-Conditions

Acceptance Criteria

Security Considerations

• Does this work make you nervous about privacy or security?
• Does this work make major changes to the system?
• Does this work implement new authentication or security controls?
• Does this work create new methods of authentication, modify existing security controls, or explicitly implement any security or privacy features?

Notes

Tasks

Definition of Done (Updated 8-28-19)

Product Owner

• [ ] Acceptance criteria have been met

UX

• [ ] Business test scenarios to meet all acceptance criteria have been written
• [ ] Usability has been validated
• [ ] Wiki has been updated (if applicable)
• [ ] Story has been tested on a mobile device (for external users only)

Engineering

• [ ] Automated test scripts have been written
• [ ] Field level and page level validation errors (front-end and server-side) integrated and functioning
  • [ ] New screens have been added to pa11y scripts
  • [ ] All new functionality verified to work with keyboard and macOS voiceover https://www.apple.com/voiceover/info/guide/_1124.html
  • [ ] READMEs, other appropriate docs, JSDocs and swagger/APIs fully updated
  • [ ] UI should be touch optimized and responsive for external only (functions on supported mobile devices and optimized for screen sizes as required)
  • [ ] Module dependencies are up-to-date and are at the latest resolvable version (npm update)
  • [ ] Errors in Sonarcloud are fixed https://sonarcloud.io/organizations/flexion-github/projects
  • [ ] Lambdas include CloudWatch logging of users, inputs and outputs
  • [ ] Code refactored for clarity and to remove any known technical debt
  • [ ] Deployed to the dev environment
  • [ ] Deployed to the stage environment

[mariahkannenberg]

Jessica's thoughts on rollout:

• Practitioners - fill out google form
• Work on external messaging
• Mid-feb, increase communications
• "flip the switch"

Risks and concerns with big bang approach:

Get users interacting with the system earlier. Double entering cases into new system starting next week? Go from narrowest of targets and spread it out.

Launch March 31 launch Unclear at this time when they'll lose access to Blackstone; sounds proprietary, so they may have to cease using it.

To mitigate risk:

• have internal court users start using the system and entering cases in both systems months before.
  • Have judge's run a trial session
• If usability testing goes well, ask them to continue to enter 1-2 petitions into the system a day moving forward. Be clear on scope of time we're asking them to invest.
• Recap with them -