1. Hyper-V Cloud Proof of Concept Kickoff Meeting <Customer Name>
<Consultant Name>
<Title>
Microsoft Corporation

2. Agenda Introductions Overview and <Customer> Needs
Engagement Objectives
Process and Organization
Schedule and Milestones
Deliverables
Next Steps and Action Items
Questions

3. Introductions: Microsoft and/or Partner
Name
Microsoft Role
Commitment
Account Executive (AM)
Part-time
Engagement Manager (EM)
Services Manager (SM)
Technical Account Manager (TAM)
Account Technical Specialist (ATS)
Infrastructure Consultant
Full-time
Project Manager (PM)
Presenter Guidance
Introduce Microsoft, partner (if applicable) and customer resources for the engagement. In smaller engagements, certain consulting roles may overlap (for example, the infrastructure consultant and security consultant), so there may not be separate individuals performing each of the activities.

4. Introductions: <Customer>
Name
Customer Role
Commitment
Project Sponsor
Part-time
Project Manager
Technical Lead
Server Engineering
Directory Services
Networking
Database Services (Microsoft SQL Server)
Storage Services
Communications
Training and User Education
Quality Assurance
Help Desk
Presenter Guidance
Ensure that required roles are represented. Confirm the commitment level of each participant - using percentage of committed time is optional.

5. Overview and <Customer> Needs
This project will result in the implementation of a Hyper-V Cloud Proof-of-Concept environment based on Microsoft products and using Microsoft services’ best practices and guidance. (Review Statement of Work)
<Customer> requires:
Demonstration of how a Hyper-V Cloud can provide a reduction in time required to deploy news services
Ability to charge back infrastructure costs to business units
Drive company business agility
<Additional customer requirements>
<Customer> success factors:
Get a more dynamic, predictable and automated infrastructure for hosting internal applications
Be able to charge back business units for hosted applications at the right price vs. services delivered
IT will act as a Service Provider and a Business Partner for <Customer>’s business groups
<Add any additional customer success factors>
Bullet items can be replaced with others in the Business Opportunity and Benefits Analysis sections of the Vision and Scope document.

6. Engagement Objectives
Situation, Goals, Outcomes and Scope
<Customer> has <X> datacenters deployed in <Locations>. Typical time for provisioning a new server for a new application is estimated to be <Y> days. The average cost for deploying these servers is approximately $<Z>.
The primary objectives for delivering the Hyper-V Cloud Proof of Concept with <Customer> are:
Demonstrate the capabilities of a Hyper-V Cloud solution which can be tightly integrated with <Customer>’s existing infrastructure, leveraging existing applications and equipment where possible.
Define how new applications will be provisioned in an automated manner, and how these provisioned services will be charged back to the business unit requesting them
Provide a framework for discussing how <Customer> may leverage both Hyper-V private cloud and Windows Azure public cloud technologies to provide greater elasticity to their environment.
Scope of the Hyper-V Cloud PoC engagement with <Customer>:
Plan and implement a PoC environment using Hyper-V Cloud infrastructure components on an isolated network. The PoC environment will be based upon Microsoft products, including Microsoft Windows Server 2008 R2 Hyper-V™ and components of the Microsoft System Center Suite.
Test the PoC environment. PoC infrastructure with be limited to 1 management and 1 capacity hosts, with up to 16 VMs under management

7. Process and Organization
Approach, Models and Definitions
The engagement is based on the Microsoft Solutions Framework (MSF), and is delivered in 5 phases
Envisioning, Planning, Developing, Stabilizing, Deployment
The engagement process will incorporate the following elements;
Communications plan
Change management
Risk and Issue management
Project organization
Assumptions

8. Process and Organization (continued)
Approach, Models and Definitions
Communications Plan may include:
<MSFT/Partner Name> is the primary point of contact for <Customer>
<Customer Name> is the primary point of contact for <MSFT/Partner Name>
Weekly status meetings (may include conference calls)
Status reporting, scheduling, issue escalation
<Day> <Time> <Time zone><MSFT/Partner Name> Project management tracking documents
Status reports, project schedule, risk and issue tracking
<MSFT/Partner Name> client checkpoint meetings with <Customer>
Steering committee meetings as needed (Customer)
Continuous internal <MSFT/Partner Name> review (Engagement Manager)

9. Process and Organization (continued)
Approach, Models and Definitions
Change Management
To ensure all parties understand the impact on resources, scope and timeline, a formal change management process will be implemented
Process
Initiating a change request
Core team review
Impact analysis
Cost, regardless of implementation
Project board review
Final decision and action

10. Process and Organization (continued)
Approach, Models and Definitions
Risk and Issue Management
A risk management section in each weekly status report will be initiated and managed throughout the project in order to monitor and manage risks related to the project
Three Major Risk Areas
Business
Technology
Project execution
Escalation Path
Core team
Project board

11. Process and Organization (continued)
Approach, Models and Definitions
Project Sponsor
Microsoft/Partner Team
Engagement Manager
Delivery Resource
<Customer> Team
Project Manager
Infrastructure
Operations
Project Organization
Some of the titles listed on this slide may need to be adjusted based upon the individuals engaged on the project.

12. Schedule and Milestones
<Insert actual project schedule timeline here>
(Insert the actual schedule from the project plan)

13. Deliverables Deliverables Description Vision and Scope
Agreement on the project scope
PoC Deployment Guide
“As-built” document defining target infrastructure
Test Matrix
Document containing a set of tasks and procedures used to validate the configured solution
Pilot Proposal
Document presenting a set of proposed “next steps” for deploying into production
Project plan
Document defining the overall timeline and associated tasks

14. Next Steps and Action Items
Solution Definition Workshop (all roles)
Understand <Customer>’s current operational infrastructure (Microsoft Active Directory, networking infrastructure, Microsoft SQL Server, storage infrastructure, etc...)
Develop PoC implementation plan and test matrix
Schedule Design Sessions
Create PoC Deployment Guide
Build PoC Environment and review Test Matrix
Proof of Concept Deployment (limited scope)
Pilot Proposal document
Handover and closeout

15. Questions?

16. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication and is subject to change at any time without notice to you. This document and its contents are provided AS IS without warranty of any kind, and should not be interpreted as an offer or commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented. The information in this document represents the current view of Microsoft on the content. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED, OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.