Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

What does this document do:

  • Outline current standard operating procedures for releasing Cloud products and services for future releases in Marine Aviation Agile Centre of Excellence (MAACE)

  • Why: Cloud deployment will use a different process compared to non-cloud production releases

 Who does this impact:

  • MAACE product owners, team leads, technical advisors

  • 360 Cloud Team

  • Change Management?

Situational Context 

  • This working document establishes a baseline understanding of TC’s internal process for Cloud releases as we shift away from legacy to new Service Management tool .

Future releases:

  • BMC Remedy Service Management Suite – a customizable Service Management tool – will replace SMGS (Service Management. – Gestion Service)

  • Change Management (Client Support) will work with MAACE Component Team 

  • MAACE project/product teams to come up with new approval procedures and pipelines.

  • Would like to figure out how to support continuous deployment with appropriate gating and approvals in place for pipelines.

 

Current procedure: 

  • Conduct and complete appropriate acceptance testing before requesting changes to PROD for production releases

  • Complete security assessment and authorization (SA&A) paperwork, if needed

  • Obtain appropriate Architecture Review Board (ARB) and Technical Architecture Committee (TAC) approvals.

  • Capture changes to any existing applications as a request in SMGS (Service Management – Gestion Service) stipulating scheduled release date.  

  • Inform [insert team members of xyz team] of proposed production changes at [is this monthly/weekly meeting] ahead of Change Approval Board (CAB) meeting on Tuesdays

  • Thursday at noon - Project/ product team need to inform x team of changes for approval of production changes 

  • Tuesday at x time – X team meets to makes final approval decision 

  • Exceptions 

  • Quicker approvals and more streamlined processes may be possible for non-web group or database group changes

    • Depending on capacity of X team, these approval requests could be made on Friday or Monday (instead of Thursday) for Cloud releases ahead of Tuesday’s CAB meeting 

  • More advance notice required for approvals if the application has an outage risk 

 

  • No labels