Pre-Initiative Artifacts

• Conversion Status Summary - of the HTTP 2 HTTPS project
• Status Website Detailed - of the HTTP 2 HTTPS project
• High Priority Tasks that are blocked by this Project
• Outstanding Issues

The website below is a pointer to an excel spreadsheet where work/counts are tracked.

WebsitesV2.xlsx

Background knowledge / Lessons Learned:

It is possible to divide the websites into a series of websites for SASD and another series of websites for RegionalSan.  It is also possible to further divide those websites into Development, QA (or testing), and Production. There are several websites in each of those groups.

Previous research on this product indicates that there will be issues with each website, we think that if there is a problem in development, then it will likely be that same problem in QA and Production, 

It seems sensible to assume there is a sequence of conversion where we will want to convert websites in development to HTTPS, then websites in QA (testing) to HTTPS, and finally websites in production to HTTPS.  

In all likelyhood, if a website converts successfully in development, then it is ready to be converteed and then tested in a QA environment. Once QA has performed testing, then it is logical to convert the website to production using a change management process.