How to Build a professional Kickoff Deck for Cloud MS Transition
Kickoff Deck for Cloud Managed Services Transition
Introduction
Often your organization has the opportunity to work with customers to manage and provide cloud managed services transition as an extension of their own internal IT. Here in this blog, we will go through the various stages of taking over those responsibilities, and how to plan and phase it in. This is a kickoff deck that you walk over with your customer. Scrumbyte is the service provider here!
Typically, these are the 4 major areas we deal with:
- Define the Scope of Services
- Build a Transition Plan
- Describe the Support Model
- Resource Plan
- Governance Model
Scope of Services
Cloud Support
- Cloud network, VM monitoring
- Cloud service management console
- Cloud Vendor interfacing
- Alert setup
- Automated custom monitoring
- Identity management
Database Management (DBMS)
- Database Administration
- Backup and Recovery
- Patching
- Database monitoring using OEM/OMC
- Database clone/refresh
- Database security
- CPU scaling
Disaster Recovery (DR)
- Monitor stand-by database
- Support failover testing
- Oracle data guard management
- File system replication
- Patching
Infrastructure Support (IaaS)
- Infrastructure as a code
- Quarterly Patching
- Infrastructure support
- VM management
- Storage management
- Proactive monitoring for infrastructure
- Load balancer configurations
Apart from this you would have the specific application software, Example Oracle E-Business Suite or SAP ERP. An Example of the services you provide for Oracle EBS is listed:
- Application and security patching with little to no downtime
- Cloning and refresh
- Concurrent processing setup and monitoring
- Support month-end and year-end processing
- Workflow monitoring
- SLA management
- Application DMZ/external setup
- EBS load balance configuration
- Oracle Enterprise Manager setup and monitoring for EBS
- Health check and assessment
- Apply automation for monitoring
- Performance Monitoring
- Log monitoring
Build a Transition Plan
Here is a simple diagram to showcase your Transition Plan. You may add wordings, however the diagram is self-explanatory.
Build a sample timeline. Below is one I have built earlier that you can use as a guideline and build your own.
Support Model
There are two important components for the support model
The first is the Incident Management Flow for the specific customer. Here is a sample flow:
You can use your own escalation management flow of your own organization. Apart from the escalation flow, you can also add the following diagram for Escalation Process. You may want to change the wording here, based on what you would like to present to the customer and how comfortable both of you are with it.
Resource Plan
Describe your resources and hierarchy.
Governance
Emphasize the following items:
- Regular status meetings between customer and OD teams (Weekly)
- Monthly Business Review
- Quarterly Business Reviews with Executive Sponsors
- Provide and discuss key statistics/risks/Mitigation
- Responsibilities fixed to team resources (Scrumbyte and Customer)
- Regular communications
- Suggest improvements/enhancements
Show your potential graphical reports that you plan to submit on a periodic basic. Add your own.
This way you can create a professional deck to present on your Kickoff meeting to keep everyone impressed. You can always improve on this by adding additional information.
Authored by Vijay Chander – All rights Reserved – 2023
