reading-traffic-management-moves-to-the-cloud2I’ve assembled an Office 365 How to Methodology based on my experiences consulting and being on the customer side of the fence from 2010 to 2015. You may have read my 12 steps blog which is a summary of steps. Migrating to the cloud especially in a regulated industry adds much complexity that must be managed with an aggressive risk management plan. These risks include organizational, regulatory, audit, workforce and technology.

What I’ve found working with companies is the following but this isn’t a comprehensive list, just a sampling:

  • There’s no complete plan
  • The project team isn’t staffed with all the disciplines and representation required
  • No risk planning was conducted
  • The business isn’t engaged and an open line of communication established
  • No product management staff to manage platform lifecycle and roadmap
  • The executive sponsor has no ideas what they have signed up for
  • The team doesn’t have experience with migrations
  • No cloud experience on the team
  • Testing isn’t formalized or there’s none at all
  • Companies expect tools will do all the work
  • Detailed platform and data inventories do not exist
  • No site ownership inventories and remediation plan
  • No comprehensive communication plan

My methodology it’s a practical one that an experienced architect can implement with a strong PM and team from the required areas or discipline. A series of documents such as template feasibility study, risk plan, project charter and team staffing and skills matrix, they help fast track and organizations path to the cloud and realize the benefits of:

  • Service cost optimization
  • Faster deployment of services and features
  • Measurable progress indicators
  • Reduced technical complexity
  • Support staffing optimization
  • Improved reach and service for mobile users, customer and business partners
  • Hardware leasing and or capital costs savings
  • Audit compliance
  • Product roadmap

Yes, there are how to guides out there but they are all tool focused mostly, using the iceberg analogy, most the complexity is below the waterline in the form of organizational complexity, nebulous policy and process, required experience, organizations ability to execute, skillsets and audit compliance.

What’s included in the methodology:

  • Cloud overview benefits presentation
  • Feasibility study template
  • Risk plan template
  • Control plan
  • Project charter template
  • Team staffing template
  • Tool installation and testing template
  • Tool configuration template
  • Migration process guide template
  • Communications plan and templates
  • Migration central site collection template

The assemble of this methodology has taken a few years to refine I’ve had help from several SMEs in the area. The fun part of this personal project was hearing from other in the industry and about their experiences.

Want to know more? Have feedback on the blog? Contact me