engagement and delivery guide - cloud and enterprise ... · web viewthe hybrid cloud...

Hybrid Cloud Foundation

Prepared by

AuthorTitleEmail

Engagement and Delivery Guide

Revision and Signoff Sheet

Change RecordDate Author Version Change Reference

12/16/2016 Author 1.0 Initial release

ReviewersName Version Approved Position Date

Engagement and Delivery Guide, Hybrid Cloud Foundation, Version 1.0Prepared by Alex Lee and Joel Yoker

Table of Contents

1 Opportunity Evaluation..............................................................................42 Overview of a Typical Engagement............................................................5

2.1 Offering/Engagement Modules.......................................................................52.2 Engagement Objectives & Deliverables.........................................................6

3 Scoping Guidelines.....................................................................................93.1 Environment assessment questionnaire........................................................93.2 In Scope.......................................................................................................113.3 Assumptions................................................................................................113.4 Scoping Standard Engagements..................................................................123.5 Scoping Nonstandard Engagements............................................................123.6 Engagement Risks and Complexity Factors.................................................13

4 Pricing Guidelines....................................................................................144.1 Time and Materials......................................................................................144.2 Fixed-fee......................................................................................................15

5 Engagement Resources...........................................................................166 Applicable Offers......................................................................................17


1 Opportunity EvaluationHybrid Cloud Foundation helps organizations explore and expand on the Microsoft Azure IaaS and PaaS platform with an approach focused on solving business problems with technical solutions. This engagement is targeted toward medium and large enterprises entertaining a significant commitment to the Microsoft Azure platform.Figure 2: Engagement Goals


2 Overview of a Typical EngagementThese engagements are fixed scope at 9 weeks for the base component (Hybrid Cloud Foundation integrated with Azure Operations Introduction, with an optional module for Azure Operations Planning (+ 4 weeks). These engagements are designed to establish foundational understanding of Microsoft Azure, to establish connectivity and initial configuration of customer’s Microsoft Azure environment to meet their needs. [Partner] assists customer with understanding recommended practices for designing and operating workloads in Microsoft Azure and in developing a broad understanding of Microsoft Azure capabilities that can be used in future projects.

2.1 Offering/Engagement ModulesThe Hybrid Cloud Foundation engagement consists of a series of solution alignment workshops which provide deep dives on key planning topics for an Azure hybrid cloud architecture. Topics include identity, subscription, compute, storage, network, security planning, and operations among others. The workshops leverage the Microsoft Services Azure Reference Architecture (AZRA) recommended practices and design patterns. Following the workshops are the design and build of up to three fairly similar subscriptions. The end delivery to the customer is multiple running subscriptions with either VPN or Express Route connectivity, extension of management systems and handover of functional specification.The core components include:

Hybrid Cloud Foundation: Comprehensive planning activities to design the customer’s subscription, administrative, naming convention, information security, and billing models. High-level design and implementation of a base networking, storage, identity and compute infrastructure in your Azure subscription model. Provide informal knowledge transfer to prepare to operate in Azure and expand Microsoft Azure usage into other scenarios

Azure Operations Introduction: Workshops and discussion to introduce key Azure Operations concepts, impacts and potential risks. Discuss what changes with the move to Azure, including recommended and required operational activities, organizational considerations, new roles and responsibilities along with service brokerage and service Integration. The resulting report provides awareness of needed changes though assessment of the customer’s operational readiness and identification of the customer’s Azure operational maturity gaps.

A standard optional module is available.


Azure Operations Planning: This optional planning module provides prescriptive guidance to address the operational maturity gaps identified in the default Azure Operations Assessment. Focus is on the details of the people, process, and technology shifts needed to adopt hybrid cloud principles. The resulting plan will provide the roadmap for the recommended operational and organizational changes and initiatives to establish key service management processes to support new Azure-based services cost effectively, efficiently, and strive for a virtually seamless service experience.

2.2 Engagement Objectives & DeliverablesPlease refer to this engagement’s SOW and WBS templates as the authoritative sources of engagement structure, activities, deliverables, schedules, and resourcing – for the core engagement delivery module and optional modules.

2.2.1 Core ModuleThe table below is a high-level overview of the engagement objectives and deliverables by phase, for the core delivery model. Table 1 - Core Objectives & DeliverablesPhase Purpose/Objective Deliverable

Envision [Partner] will lead a 1-2 remote meetings prior to the project kickoff to assist in preparing prerequisites and dependencies. [Partner] will then lead a formal project kickoff meeting to begin onsite activities.


Phase Purpose/Objective Deliverable

Plan Align customer requirements with Microsoft Azure capabilities and recommended practices. Note: Workshop modules can either be delivered contiguously over a period of 32 hours delivered independently to focus groups over the scope of the engagement. Topics include:

Subscription Model Planning

Information Security Planning

Billing Process Planning Network Planning Identity Planning Storage Planning Azure Operations

Conduct Solution Alignment Workshops. Summarize customer design decisions in the SAW Summary Report.Functional Specification document based on AZRAAzure Operations Introduction, Next-steps report

Build Assist customer with configuring Azure.

Subscription configuration Networking configuration ExpressRoute Planning Storage configuration Identity configuration Management, Monitoring

and Maintenance configuration

Compute configuration

Functional Azure environment

Stabilize Assist with testing activities.Provide a demonstration of the Solution and recommended practices for operations and management to customer staff.

Test cases

Deploy

2.2.2 Optional Module – Azure Operations PlanningThe table below is a high-level overview of the engagement objectives and deliverables for the optional delivery module.


Table 2 – Optional Objectives & DeliverablesModule Purpose/Objective Deliverable

Azure Operations Planning

An incoming questionnaire to assess and understand the current state of Azure operations.A series of workshops, discussions focused on:

Service Readiness (Service Map and Description)

Process Readiness (integration and broker guidance, Azure subscription RACI)

Operational Readiness (role and operational guidance, Azure monitoring)

People Readiness (role and operational guidance)

Pre-engagement questionnaireService mapService descriptionService integration guidanceService broker guidance Azure RACI Next-steps report


3 Scoping Guidelines

3.1 Environment assessment questionnaireThe questions listed below should be asked to the customer to help you scope the engagement. The could be general questions, such as what is driving the need for this project? Table 3 – Environmental assessment questionnaire

Question Answer

1. Does the customer have an Azure Enrollment already?

2. Does the customer consume other public cloud services already, e.g. AWS?

3. After the Hybrid Cloud Foundation, what workloads or services are the customer planning to deploy/consume

4. Does the customer already have services enabled in Azure?

5. Is the customer a process oriented organization, does it have the breadth and depth to consume 4 weeks of AZOP Planning?

6. Have the customer outsourced its IT operations, will [Partner] be working multiple parties for the design and build.

7. Does the customer have an existing process governance model? If so, can they provide the specifics for incident, problem, change and release management?

8. How well does the current organizational model support IT services? Are there any organizational or cultural obstacles to realizing customer future services?

9. What has been the area of greatest frustration in the customer organization with respect to IT operations?


Question Answer

10. What is the current scope of Service Level Agreements?

To what extent are Service Catalogues and Service Quality Plans implemented? How effective are they?

11. How are the support & management capabilities implemented currently?

a) Consumer & Provider Portalb) Usage & Billingc) Service Reportingd) Service Monitoringe) Service Managementf) Configuration Management (CMDB)g) Authenticationh) Authorizationi) Directoryj) Data Protectionk) Deployment & Provisioningl) Process automationm) Fabric Managementn) Network & Storage Support


3.2 In ScopePlease refer to this engagement’s SOW and WBS templates as the authoritative sources of engagement structure, activities, deliverables, schedules, and resourcing. For a high-level overview, please refer to Section 4 – Overview of a Typical Engagement (above). The figures below list the scope and modules available.Figure 3: Engagement Scope

Figure 4: Engagement ModulesPlease refer to this engagement’s SOW and WBS templates as the authoritative sources of engagement structure, activities, deliverables, schedules, and resourcing. For a high-level overview, please refer to Section 4 – Overview of a Typical Engagement (above). Anything not listed in the modules, objectives, and deliverables indicate out of scope work.

3.3 AssumptionsPlease refer to this engagement’s SOW and WBS templates as the authoritative sources of engagement structure, activities, deliverables, schedules, and resourcing.


Subscription model and governance, Naming conventions, deployment etc.Subscription DesignExtend current AD and DNS to AzureEnable Azure AD for Azure governanceIdentityEstablish and plan for Express Route, Virtual Networks, IP Plan, network security etc.NetworkingExtend current monitoring for IaaS, enable monitoring of Azure and PaaSMonitoringExtend current patch management solution to include Azure IaaS servicesUpdate ManagementExtend current AV & Malware protection to include Azure IaaS servicesAntivirus/MalwareExtend or deploy new disaster/recovery and backup solution for Azure IaaS servicesBackup / DRDefine requirements for chargeback / show-back and enable the tools and processesChargeback

3.4 Scoping Standard EngagementsAs discussed in Section 4 – Overview of a Typical Engagement (above), there are mandatory and optional modules in this offering. We expect the mandatory modules to remain unchanged and lightweight, as to accommodate a large number of customer scenarios. As additional business outcomes are identified we will add more recommended and optional modules.

Please contact us with suggestions for additional business outcomes and optional modules.

The standard engagement is primarily concerned with getting the customer enable to consume services in Azure, based on the guidance and recommended practices detailed in the Azure Reference Architecture (AZRA). The standard engagement integrates Azure Operations Introduction, intended to identify any areas of risk with the customer’s operational processes as they introduce Azure into the environment.The Azure Operations Planning module is a recommended, but optional, addition to increase the successful adoption and management of the new Azure environment. These additional four (4) weeks help the customer devise a clear plan to address any areas of risk and operational maturity gaps through which they can more efficiently operate their Azure resources.

3.5 Scoping Nonstandard Engagements3.5.1 Azure Operations Implementation Some customers seek additional assistance with the execution of Azure Operations Planning to implement the people, process and technology changes and establish the desired Azure operational processes. This implementation phase is typically addressed with an additional 3-6 week time-boxed effort based on known customer maturity and complexity, but can also be custom scoped after the Azure Operations Introduction and Azure Operations Planning phases complete. Note that the Introduction and Planning phases must complete before starting the Implementation phase. It is recommended to include an Architect from the IT Service Management team to identify the appropriate option.

3.5.2 Pilot Workload Deployment The Pilot Workload Deployment module is optional. This module adds value for the customer by working with them to plan, deploy, and configure a single or more workloads in Azure. The goals are to: apply the recently learned patterns and practices from AZRA and AZOP, utilize the recently configured Azure subscription(s), and demonstrate the value of consuming an application from the cloud.


During this optional module, [Partner] works with the customer to: Identify appropriate workload or workloads. Conduct an Architectural Design Session in order to develop the workloads’

high level architecture. Assist with building VM images for the workload, if required by the design. Assist with deploying and configuring the workload in Azure.

Custom scoping is required. We recommend timeboxing the deploy and configure phases.

3.6 Engagement Risks and Complexity FactorsTable 2: Potential risks for this engagementRisk Description Rating MitigationCustomer not prepared to Operate

Customer does not have the people, process and technology in place to integrate Azure into their operational fabric. Operational fear, pain and lack of governance may stall Azure consumption and growth beyond foundation

Medium

Include Azure Operations Planning and consider custom Operations Implementation scope addition or follow on effort.

Customer not able to engage with [Partner] at 9 consecutive weeks

Customer and IT staff are overloaded with work, need to focus on the IT-Operations and incidents, decisions take longer than expected etc. Things like these can prolong the project and it is important to consider this in the staffing and allocation plan.

Low Initially planning and agreement with customer on timeline, proper resource allocation and include room for slack if needed.


4 Pricing Guidelines

4.1 Time and MaterialsPlease refer to this engagement’s SOW and WBS templates as the authoritative sources of engagement structure, activities, deliverables, schedules, and resourcing. The following tables outline the common delivery models, example cost, and staffing model.

4.1.1 Sample Cost By Delivery Model Table 3: Risk and sample cost per delivery model

Delivery Model Risk Level Sample Cost

Core – Standard Engagement: HCF & AZOP Introduction Low

Core – Standard Engagement: HCF & AZOP Introduction + AZOP Planning

Low

Non-Standard Engagement: HCF & AZOP Introduction + AZOP Planning+ Pilot Workload Deployment

(ex.,1 day ADS + 10 days deploy)+ AZOP Implement

(ex., 6 weeks)

Medium - High

4.1.2 Estimated Resource Hours By Delivery ModelTable 4: Estimated resource hours – Core module

Delivery Model Resource AreaHours (est)

Core – Standard Engagement: HCF & AZOP Introduction(9 weeks)

Engagement Manager (10%) Engagement Management 40Project Manager (15%) Project Management 56Solution Architect (20%) Solution Architecture (HCF) 104Senior Consultant (HCF) Azure: Hybrid Cloud

Foundation Delivery 360

Junior Consultant (HCF) Azure: Hybrid Cloud Foundation Delivery 320

Senior Consultant (ITSM Introduction)

Operations: Operations Introduction Delivery 48


Table 5: Estimated resource hours – Core module + AZOP Planning

Delivery Model Resource AreaHours (est)

Core – Standard Engagement: HCF & AZOP Introduction+ AZOP Planning(13 weeks)

Senior Engagement Manager (10%) Engagement Management 40Project Manager (15%) Project Management 64Solution Architect (20%) Solution Architecture (HCF) 104Solution Architect (ITSM) Solution Architecture (ITSM) 20Senior Consultant (HCF) Azure: Hybrid Cloud

Foundation Delivery 360

Junior Consultant (HCF) Azure: Hybrid Cloud Foundation Delivery 320

Senior Consultant (ITSM Introduction)

Operations: Operations Introduction Delivery 48

Senior Consultant (ITSM Planning)

Operations: Operations Planning Delivery 160

Senior Consultant (Operations Manager)

Operations: Operations Planning Delivery 40

4.2 Fixed-feeThere are no fixed fee estimations done for this delivery.


5 Engagement ResourcesTable 6: Engagement resources -Allocation and Responsibilities

Role Time Allocation ResponsibilitiesEngagement Manager

Ad-hoc for duration of engagement

▪ Serves as a single point of contact for billing issues, personnel matters, contract extensions, and [Partner] project status

Project Manager

6 hours per week for duration of engagement

▪ Manages day-to-day activities of the [Partner] team.▪ Managed Risks and Issues▪ Manages Status Reporting and Meetings▪ Coordinates the activities of the [Partner] team to

deliver according to the project schedule.Solution Architect (Azure: HCF)

12 hours per week for duration of engagement

▪ Leads Solution Alignment Workshop▪ Assists with Microsoft Azure configuration and other

Solution build activities▪ Assists with Solution testing▪ Supports Solution Walk Through

Solution Architect (ITSM)

Ad hoc during 4 weeks of AZOP Planning

[OPTIONAL] if including Azure Operations Planning]▪ Oversight of the Operations Consultants for the Azure

Operations Plannning work stream.

Azure Consultants - 1 Senior - 1 Junior

Senior – Full time all 9 weeks of HCF

Junior – Full time all 8 weeks of HCF

▪ Leads the Solution Alignment Workshop▪ Leads Microsoft Azure configuration and other Solution

build activities▪ Leads Solution development activities▪ Leads Solution testing▪ Leads Solution walk through

Operations Consultant

Half time during week 1 and 2

Full time during 4 weeks of AZOP Planning

▪ Leads the Azure operations workshops[OPTIONAL if including Azure Operations Planning]▪ Leads the Service delivery work▪ Leads the Service Integration work▪ Leads the Role and Responsibilities work▪ Leads the Azure Operations guidance workshop

Operations Manager Consultant

Full time during week 3 of AZOP Planning

[OPTIONAL if including Azure Operations Planning]▪ Leads the installation and configuration of System

Center Operations Manager▪ Assists the Azure Operations guidance workshop


6 Applicable Offers

Offer Name Description Justification Service

Type

Duration

Hybrid Cloud Management

Introducing cloud capabilities can lead to a range of benefits including lower costs, on-demand resource provisioning, improved management capabilities, increased innovation and decreased time to market. Delivery of Hybrid compute can also introduce additional complexities that may make existing operational practices challenging. [Partner] offers Hybrid Cloud Management to help you overcome these challenges with improved operations, monitoring and management across on-premises and public cloud for Linux and Windows workloads, no matter how complex your environment.This Offer is modular, aligned to the OMS scenarios:

Log Analytics Backup and Recovery IT Automation Security and Compliance

You can sell and deliver this Offer as one engagement encompassing all scenario, or each scenario independently.

Enabling the customer to utilize Operations Management Suite and the related services there.

[PARTNER]

Depends on scenarios selected

Service Operations and Governance

The Service Operations & Governance offerings shares the recommended roles, processes and activities for organizations to become a cloud service provider. [Partner] can help your organization achieve Cloud Operations readiness by assisting with the following:Service Delivery – helping define consumer requirements into Cloud Services and to manage the delivery of these services throughout the service lifecycle.Service Lifecycle Management – leveraging Microsoft recommended practices for managing the Cloud Services lifecycle Process Readiness - [Partner] will provide prescriptive guidance on the processes needed to manage your Service ConsumersOperational Activities – Operations is vital for delivering cloud Services, the end to end

This portfolio of offerings focuses on the people and process needs to align traditional ITSM into Modern Service Management by sharing recommended practices and principles for team organization and process integrations to become a cloud based service provider.

[PARTNER] and ITSM

Varies


management of hybrid services need to be managed, monitored and maintained correctlyCloud Roles & Responsibilities – provide prescriptive guidance on the necessary roles and responsibilities to manage Azure based cloud services

Table 9: Offers to consider for delivery after the engagementOffer Name Description Justification Servi

ce Type

Duration

Hybrid Cloud Automation

The Hybrid Cloud Automation Offer and IP is designed to enable our customers, both Enterprises and Service Providers to automate their environments, processes, and operations both on During the design and deployment of their automation solution, organizations will work with [Partner] architects to strategically identify and activate automation capabilities to help them realize the full value of a Windows Server and System Center deployment.

The Hybrid Cloud Automation Offer combines Microsoft technologies and services to help organizations more quickly design and implement an automation solution that is tailored to fit their business and IT needs.

[PARTNER]

Varies

Capacity Optimization and Cost Show back

Implement an Azure cost reporting framework to provide cost and capacity utilization reporting

Over consumption and underutilization of Azure resources can hinder growth of Azure footprint. This engagement provides the tooling and insight to manage the financial element of Azure Operations

Fixed fee, IT Service Management

2 weeks


engagement and delivery guide - cloud and enterprise ... · web viewthe hybrid cloud...

Documents