...
- Provision systems, VMs, based on initial architecture plan.
- New raft-test and raft-prod systems in place. To replace existing RAFT I servers.
- Await decision on budget for online help systems. bi-help-dev installed on temporary system so documenation staff can begin work.
- Update datacenter SLAs with technical, financial, business contact information.
- Developing blanket SLA between business-support and Business Intelligence team.
- Draft in progress. Service Levels Development
- Training curriculum, work with Training to ramp-up Help Desk (business-support).
- Stakeholder engagement: Trying to move design documents to wiki for better collaboration, resources limited.
- Develop RAFT escalation scripts from Tier 2 (business-support) and Tier 3 (raft-support).
- Phased usability test plan underway with phased rollout of RAFT functionality (Agile?)functionalitY: Usability & Accessibility.
Monitor and Control
- If actual dates do not match previously expected dates, update calendar.
- business-help and business-intelligence teams to perform smoke tests for every patch or update during burn-in period.
- If sending outside of IS&T, send draft release announcement to IS&T communications team at least 2 business days prior to release.
- Inform release-core@mit.edu, pipeline of release at least 1 business day prior to release.
- Release (Send announcement, deploy final production release, etc.)
- Second architecture review required, same reviewers, after May pilot release.
- Revise smoke tests and escalations as needed.
...