Skip to content
This repository has been archived by the owner on Feb 7, 2025. It is now read-only.

Readiness Review Template #1439

Open
2 tasks
Adrian-Brewster opened this issue Oct 16, 2024 · 13 comments
Open
2 tasks

Readiness Review Template #1439

Adrian-Brewster opened this issue Oct 16, 2024 · 13 comments

Comments

@Adrian-Brewster
Copy link

Adrian-Brewster commented Oct 16, 2024

Story

As a Jurisdiction, so that I can score my readiness to move to production, I need attendee a readiness review that where all relevant stakeholders gain consensus on readiness and confirm a date to move go live.

Acceptance Criteria

  • A competed template that will be used to facilitate the readiness review

Tasks

  • Also link in a checklist for post go-live verification (e.g. checking the micro character encoding)
@brick-green
Copy link

@Adrian-Brewster Can you provide an update for this ticket?

@brick-green
Copy link

Also, can you provide links to the document(s)?

@Adrian-Brewster
Copy link
Author

I fear the most current update I have on this is that Rebecca did not see much value in having it. There is currently a checklist that the Deloitte folks are using that track things that need to be completed before moving to production. I'll bring this up to the team tomorrow and see how we want to proceed.
CA - ETOR Readiness Review.docx

@brick-green
Copy link

@Adrian-Brewster Did you get a chance to bring this up? What should we do with this ticket?

@brick-green
Copy link

@scleary1cs
Copy link
Contributor

We have lots of messages in the queue, what is the line in the sand that CA wants at go-live? Need to capture this as an action item in the readiness review template.
@halprin did I capture that right?

@halprin
Copy link
Member

halprin commented Dec 6, 2024

There are a lot of messages piling up in CDPH's SFTP server in the UCSD production folder. What does CA partners want to do with these pre-existing messages when we go-live? Should we send all these older messages through? Should we delete the older messages, so only new messages post-go-live go through? Or maybe there is some other outcome they want.

@brick-green
Copy link

@kwright-bio Is going to ask about the production messages on SME call 12/11

@brick-green
Copy link

@kwright-bio asked on the SME call about about the production messages in the CDPH production folder. UCSD does not want any of those old results so that folder will need to be cleared out prior to going to production.

@brick-green
Copy link

@amcnuttJMC reached out to Marty. Waiting for response

@kwright-bio
Copy link

Hi - sorry for the delay in update. At some point, I chatted with Sam / Marty, and they were going to see if there was anything the APHL ETOR proceses used. I have a checklist I got in return, but asked a question about it and have not heard back. Will follow up and make sure I copy others too after the initial one off.

@amcnuttJMC
Copy link

Update: Sent to Marty and Sam and they wish to discuss this on Tuesday January 14, 2025's program meeting

This includes the APHL template which information was used from to make the current CA Readiness Review. Both included here: APHL RR.docx
California - ETOR Project Readiness Review.docx

@amcnuttJMC amcnuttJMC assigned kwright-bio and unassigned amcnuttJMC Jan 10, 2025
@kwright-bio
Copy link

Discussed on 1/14 meeting. Emailed the document out to CDC / Deloitte team members and uploaded to Sharepoint. Requested their feedback on what additional documents are needed if any and if they wanted adjustments to this one.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants