Page History

We are working on the release of RAFT II. This is a major release. This checklist tracks is the current release path of RAFT II to the service operations, primarily from the Business Intelligence development team to Customer Support, Training, and Server & System Administration. 

Initiation

• Points of contact and release team defined in Roster.
• Training teams from IS&t and COEUS engaged; Training Plan.
  • Critical Path: Need stable test environment.
• Usability team engaged; Usability & Accessibility.
• business-support team engagement, SLA in development: Service Levels Development
• Stakeholder committee schedule in place, core business users signed up for rolling usability-test plan.

Planning

Change Management

• Enter release date, and other significant dates, on Change Communications Calendar.
  • Exchange resource name: IS&T: Change Communications
  • When these dates change, communicate to ist-pipeline list.
  • This has not been done in a while, dates have changed a lot.Are hard dates (i.e. less than two weeks slippage) ready?
• Planned major milestones recorded on wiki home page.
• Send announcement and change log to ist-pipeline@mit.edu, stakeholder list once release is complete.
• Update any known open issues (Jira, Request Tracker) affected by release and close.
• Search http://ist.mit.edu.ezproxyberklee.flo.org and http://kb.mit.edufor any articles that would be invalidated by release and update as needed. Contact istweb@mit.edu if you are not sure how to update this documentation.
• Contact IS&T Communications for public release announcement.
  • If sending outside of IS&T, send draft release announcement to IS&T communications team at least 2 business days prior to release.
• Inform ist-pipeline@mit.edu, pipeline of release at least 1 business day prior to release.
• Consider how to support early adopters or pilot users, phase out current version?
  • Pilot release in May, community release in June. Still no hard transition plan for RAFT I users?
• Internal IS&T internal architecture-review team formed. Six-week code burn-in period required between code-completion and go-live.
• Code management/versioning and continuous integration plan with release engineer. Deploy from Bamboo or directly from SVN.
  • Awaiting stable test release to raft-test for system operators to review the install.
• Review need to de-support of previous version(s), communications to current users.
• Create communication plan, based on stakeholders identified in prior steps.
• Create smoke-test plan with business-support team. Due before June go-live.

Executing

Configuration Management

• Critical Path: Need stable test environment!
• Migrating from RAFT I environments to new, clean VMs for RAFT II
  • raft-test in place, needs PHP downgrade?
  • raft-r1, new raft production, does not exist yet
  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 drupal-based 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.

Release and Deployment Management

• OLA: business-support team engagement, OLA in development: Service Levels Development
  • Developing blanket
  SLA
  • OLA 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). Support Escalations Outline
• Phased usability test plan underway with phased rollout of RAFT functionalitY: Usability & Accessibility.

Monitor and Control

• Code management/versioning and continuous integration plan with release engineer. Deploy from Bamboo or directly from SVN.

Evaluation and Testing

• See "evaluators" list at right. Responsible parties for internal evaluation. Must sign off. Second architecture review still required by this group.
• Input and sign-off by Usability Team: Usability & Accessibility Reports.
  • Stakeholder committee schedule in place, core business users signed up for rolling usability-test plan.
• If actual dates do not match previously expected dates, update calendar.
• BI Team to provide smoke-test/system health page for Customer Support?
  • • business-help and business-intelligence teams to perform smoke tests for every patch or update during burn-in period (six week from go-live).
  • 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.

  Closing

  Knowledge Management

  • Training Plan
    • Training mutual venture of SE Training team and COUES Training team.
    • Training curriculum, work with Training to ramp-up Help Desk (business-support).
  • Online Help: SE Training, Mark Wiklund.
    • are we still doing this?
  • Develop RAFT escalation scripts from Tier 2 (business-support) and Tier 3 (raft-support). Support Escalations Outline
  • Send announcement and change log to release-core@mit.edu, stakeholder list once release is complete.
  • Update any known open issues (Jira, Request Tracker) affected by release and close.
  • Search http://ist.mit.eduand http://kb.mit.edufor any articles that would be invalidated by release and update as needed. Contact istweb@mit.edu if you are not sure how to update this documentation.