LCS - Utilizing the Pre-Launch Checklist
Before an application initially goes live in Production, a pre-launch checklist needs to be filled out and approved. Steps to take are outlined below.
- Start a Pre-Launch Checklist
- Review process
- Sign-off of the Pre-Launch Checklist
- Turning application status to Live
Start a Pre-Launch Checklist
- When the developer or Org Admin contacts the LCS team that the application is ready for review (see LCS - Before setting your application live), the developer or Org Admin should copy/download the newest version of the Pre-Launch checklist found in the LCS Info template folder.
- The application name should be entered on the form and the filename changed to the application name.
- The checklist should be saved into a newly-created folder, folder name=application name, into the In Progress Checklist folder .
- The developer should begin filling out the checklist according to directions in the checklist.
Review process
- The LCS team will do a review of the minimum security requirements (see the requirements and LCS - Best Security Practices), the review document or an accessible link to it should be added to the In Progress folder described above.
- After the LCS team completes the review, the developer should make appropriate changes or record in the checklist why changes were not made.
Sign-off of the Pre-Launch Checklist
- Each School/College/Division (S/C/D) will have a different approval process so the developer should work with the Org Admin of their S/C/D to see who else needs to approve the Pre-Launch Checklist.
- Once the checklist is approved by the appropriate people, move the folder containing the review and checklist from the In Progress Checklist folder to the Completed and Signed Checklist folder.
Turning application status to Live
- Let the LCS team know when the Org Admin has changed the status to Live or if no Org Admin exists, inform the LCS team to change the application status.
- Remember to update the IT Inventory accordingly.