User's blog

CIN Methodology for Hyperscaler Transition

CIN Methodology for Hyperscaler Transition

  • accelerates projects by using a proven methodology including best practices and the knowledge about hyperscaler transitions. This makes it predictable, minimizes the  migrationrisks and guarantees you customer satisfaction.
  • offers an end-to-end process from project initiation through recommendations to execution, including a potential subscription for ongoing cost optimization, including automatic tracking of changes.

The overall project will be delivered in sprints of 2 weeks with one or more Teams of Ten within a defined timeframe, focusing on business processes and not on functionality.

Initiate

Offer customer support to find the future datacenter setup and landscape definition

Explain our methodology

  • Template for an implementation project with know-how from previous implementations
  • Agile project methodology
  • Fixed price
  • Transparent delivery structure

We convince with knowledge about the potential solution scope and transitions options. Our extensive experience ensures low risk and fast time to value.

We did the big hyperscaler transitions in the world

Positioning of a discovery phase based on the customers transition volume, the source and target point of presences including legal and compliance boundaries

Discover

Provide a transition-ready solution design and architecture documentation. This step is important to ensure fast project implementation. Fixed price offer for the delivery.

Transition

  • Start Project by creating a detailed backlog based on the saving targets. 
  • All areas for savings will be detailed out in the project management environment for audit purposes.
  • Setup the meetings based on the meeting structure
  • Explain the different dashboards for the customer 
  • Deliver sprints every 2 weeks
  • First savings within 1 months
  • Show and tell (demo) sessions and user acceptance tests after each sprint

Cool-Down

The Cool Down completes the corresponding phase:

  • Bug-Tracking during the cool down phase (predefined redmine dashboards)
  • Final acceptance by the customer (Status Closed for all User Stories)
  • Documentation: Handover the project content after the end of the project
  • Customers can import these files into their own workspace or own project management instances and use them as documentation or as starting point for follow-up projects.