datacenter infrastructure and management - … · web vieworganizations today are demanding...

Vision and Scope

9-May-23Version 2.0 Final

Prepared by

<partner name>

Datacenter Infrastructure and Management Solution Offering

Datacenter Infrastructure and Management

MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, our provision of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. The descriptions of other companies’ products in this document, if any, are provided only as a convenience to you. Any such references should not be considered an endorsement or support by Microsoft. Microsoft cannot guarantee their accuracy, and the products may change over time. Also, the descriptions are intended as brief highlights to aid understanding, rather than as thorough coverage. For authoritative descriptions of these products, please consult their respective manufacturers.© 2013 Microsoft Corporation. All rights reserved. Any use or distribution of these materials without express authorization of Microsoft Corp. is strictly prohibited.Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

iiDatacenter Infrastructure and Management, Version 2.0 FinalPrepared by [Delivery Consultant] “Vision and Scope" last modified on 4 Dec. 13


Revision and Signoff Sheet

Change RecordDate Author Version Change Reference

[Date] [Delivery Consultant] # Initial draft for customer review

ReviewersName Version Approved Position Date

iiiDatacenter Infrastructure and Management, Version 2.0 FinalPrepared by [Delivery Consultant] “Vision and Scope" last modified on 4 Dec. 13


Table of Contents

1 Introduction ...............................................................................................52 Opportunity Statement ..............................................................................6

2.1 Opportunity Statement ..............................................................................................6

3 Project Vision and Scope ............................................................................83.1 Vision Statement .......................................................................................................83.2 Benefit Analysis .........................................................................................................93.3 Project Requirements ................................................................................................93.4 Business Requirements ...........................................................................................103.5 Functional Requirements .........................................................................................103.6 Operational Requirements .......................................................................................103.7 Technical Requirements ..........................................................................................11

4 Scope of the Project .................................................................................124.1 Project Objectives ....................................................................................................12

4.1.1 Business Objectives ......................................................................................12 4.1.2 Technical Objectives .....................................................................................12

4.2 Scope ......................................................................................................................134.2.1 In Scope ..........................................................................................................13 4.2.2 Out of Scope ...................................................................................................14

4.3 Acceptance Criteria .................................................................................................154.4 Operational Critieria ................................................................................................15

ivDatacenter Infrastructure and Management, Version 2.0 FinalPrepared by [Delivery Consultant] “Vision and Scope" last modified on 4 Dec. 13


5 Risk Management ....................................................................................171 Introduction .................................................................................................72 Opportunity Statement .................................................................................8

2.1 Opportunity Statement ..........................................................................................8

3 Project Vision and Scope .............................................................................103.1 Vision Statement ..................................................................................................103.2 Benefit Analysis ....................................................................................................113.3 Project Requirements ...........................................................................................113.4 Business Requirements .......................................................................................123.5 Functional Requirements .....................................................................................123.6 Operational Requirements ..................................................................................123.7 Technical Requirements ......................................................................................13

4 Scope of the Project ....................................................................................144.1 Project Objectives .................................................................................................14

4.1.1 Business Objectives ...................................................................................14 4.1.2 Technical Objectives ..................................................................................14

4.2 Scope .....................................................................................................................154.2.1 In Scope .........................................................................................................15 4.2.2 Out of Scope .................................................................................................16

4.3 Acceptance Criteria ..............................................................................................174.4 Operational Critieria .............................................................................................17

5 Risk Management .......................................................................................19

vDatacenter Infrastructure and Management, Version 2.0 FinalPrepared by [Delivery Consultant] “Vision and Scope" last modified on 4 Dec. 13


viDatacenter Infrastructure and Management, Version 2.0 FinalPrepared by [Delivery Consultant] “Vision and Scope" last modified on 4 Dec. 13


1 Introduction<Text in this format indicates instructions to the writer/editor of the document and should be removed before providing the document to the customer>.<Build an executive summary that is specific to the particular engagement. This draft was provided to form the backbone/background to the executive summary content. It should be modified and abbreviated to address TDM and BDM audience. Use business terms, not technical language.>[Customer] has selected the Microsoft Datacenter Infrastructure and Management offering to consolidate and optimize management and control of its infrastructure system and application platforms, as well as to address some key challenges around the design and deployment of a private cloud infrastructure. The goal of the Datacenter Infrastructure and Management solution offering engagement is to help organizations develop and implement private cloud infrastructures quickly while reducing both complexity and risk. The IaaS PLA provides a reference architecture that combines Microsoft software, consolidated guidance, and validated configurations with partner technology such as compute, network, and storage architectures, in addition to value-added software components.The private cloud model provides much of the efficiency and agility of cloud computing, along with the increased control and customization that are achieved through dedicated private resources. By implementing private cloud configurations which align to the IaaS PLA, Microsoft and its services and hardware partners can help provide organizations both the control and the flexibility that are required to reap the potential benefits of the private cloud.The IaaS PLA utilizes the core capabilities of the Windows Server operating system (OS), Hyper-V, and System Center to deliver a private cloud infrastructure as a service offering. These are also key software components that are used for every reference implementation. The target architecture is implemented through application of the pre-defined solution patterns identified in the PLA, featuring selected components of the Microsoft Windows Server Hyper-V and System Center solution. Such approach secures repeatability and standardization of the core capabilities, reducing project’s risk, while allowing extensive customization and adaptation of the solution to the customer’s specific needs and environment.The purpose of this document is to provide a sufficient level of details about each element of the solution architecture, explaining what the project will build and deploy. This document is an outcome of an envisioning meeting during which all requirements (business, functional, technical, operational) are shared and discussed. This Vision and Scope document does not cover the implementation strategy of the solution or its design. Implementation information is contained in the Scope of Work and outcome documentation of the Solution Alignment Workshop.

Datacenter Infrastructure and Management, Version 2.0 FinalPrepared by [Delivery Consultant]“Vision and Scope" last modified on 4 Dec. 13


2 Opportunity Statement<Business opportunity section should briefly present key business challenges (business opportunities) relevant for the scoped/planned Datacenter Infrastructure and Management engagement. Focus on using the business language. Section should demonstrate. This chapter should clearly demonstrate contractor understands of the customer’s business and operational environment and of its desired future state. This sets the overall project context.>

The Datacenter Infrastructure and Management offering reference architecture combines Microsoft software, consolidated guidance, and validated configurations with partner technology such as compute, network, and storage architectures. This offering can help organizations adopt:

End-to-end monitoring - Monitor infrastructure and applications across the enterprise Private cloud- Infrastructure spanning multiple physical locations to support the organization in the event of

catastrophic failure of the primary datacenter Hybrid cloud - Extending enterprise IaaS into the public cloud using Windows Azure, and extending fabric

management across both private and public cloud to form a hybrid cloud infrastructure Virtual desktop infrastructure – VDI solutions built using the Microsoft virtualization and management

platform Monitoring, incident and change management - Enabling the upgrade or planning of a large deployment

of monitoring, incident and change management of backup using System Center.

2.1 Opportunity Statement<This section should describe customer’s current situation and need for the project. In particular, section should present a particular customer opportunity and discuss impact of addressing that opportunity (infrastructure services innovation, maturity enhancement, cost avoidance, operational streamlining and using knowledge). Section could also present customer’s challenge/problem and the business/operational impact of addressing that problem (IT and business units partnership, cost reduction, alignment of strategy and technology, business agility, end-user satisfaction, process optimization). The Opportunity Statement is written using business language. Opportunity Statement demonstrates that delivery team understands the customer’s situation, and it provides the project team and other readers with the strategic context for the remaining sections.>

Organizations today are demanding dynamic, agile systems that can support their constantly changing business needs. IT decision-makers are challenged to quickly deploy well-architected complex data center environments and processes in order to support increasing business demands. To maximize the value of their next deployment organizations should consider:

Eliminating disparate systems – Owning and maintaining multiple infrastructure and management systems is taxing on IT budgets and resources

Removing infrastructure silos – Allowing each group to purchace and maintain their own IT assets encourages poor utilization patterns

Managing service levels – Many applications require higher service levels and organizations must reduce the impact of both planned and unplanned outages

Datacenter Infrastructure and Management, Version 2.0 FinalPrepared by [Delivery Consultant] “Vision and Scope" last modified on 4 Dec. 13


Lowering the cost of IT – Reliance on Tier 1 systems escalates the cost of delivering and maintaining infrastructure, stifling an IT organization’s ability to transform alongside the changing needs of the business.



3 Project Vision and Scope

3.1 Vision Statement<Guidelines for a Project Vision statement:

Purpose: Establish the project’s purpose and introduce vision of the engagement’s success and solution’s value for the customer.

Length: One paragraph at maximum. Best Vision statements are written in one sentence.

Guidelines: Balance all of the interests to arrive at a single vision statement; bring to light any enterprise architecture implications early.

Clearly and concisely describe the future, desired state of the customer’s environment when the project is complete. This can be a restatement of the opportunity; however, it is written as if the future state has already been achieved. This statement provides a context for decision making. It should be motivational to the project team and to the customer.

Why: A shared Vision Statement among all team members helps ensure that the solution meets the intended goals. A solid vision builds trust and cohesion among team members, clarifies perspective, improves focus, and facilitates decision making.>

<Example follows.>

[Customer] has the vision of implementing a consolidated, automated and optimized Datacenter Infrastructure and Management solution, building an integrated service management capability across heterogeneous and highly complex private cloud ecosystem.This project fits into this vision by providing key functionalities and capabilities required to deliver integrated IT service management vision.



3.2 Benefit Analysis< Benefit analysis section describes how the customer will gain value from the proposed solution. Section should connect the business goals and objectives with specific functional requirements to be realized from the project. These expectations should be clearly stated and be specific, measurable, attainable, realistic and timely (SMART framework). Section could also be extended through addition of following sub-sections:

3.2.1. Business goals and objectives

3.2.2. Business metrics

3.2.3. Business assumptions and constraints

3.2.4. Benefits statement

Why: Benefits analysis demonstrates that contractor fully understands the customer’s situation. It also defines the customer’s business needs, which may provide vital information when making solution and technology recommendations.>

Through implementation of the integrated Datacenter Infrastructure and Management solution [Customer] is aiming to gain the following benefits:

Flexible storage offers diverse storage choices that deliver performance, efficiency, and innovation while taking advantage of industry-standard hardware.

Continuous availability provides cost-effective, highly available services with protection against a wide range of failures and outages.

A complete virtualization platform delivers a fully isolated, multi-tenant environment with tools that can help ensure service level agreements (SLAs) are met, monitor resource use for reporting, and support self-service delivery.

Connectivity to cloud services using a common identity and management framework for more secure and reliable cross-premises connectivity.

Infrastructure foundation for Hybrid Cloud, Virtual Desktop Infrastructure (VDI), and Large or Complex Deployments

3.3 Project Requirements<Identify what the solution must do. These requirements can be expressed in terms of functionality (for example, a registration Web site solution will allow the users to register for events, arrange for housing, and so on) as well as the rules or parameters that apply to that functionality (for example, the user can only register once and must stay in housing approved by the travel department). Requirements exist at both the user level and the organizational level. Please refer to the results of the Solution Alignment Workshop, as well as relevant IaaS PLA documentation to build the content of this section.

Please edit recommended text in order to reflect specifics of the particular scenario.



Why: User and organizational requirements are the key inputs to developing product scope and design strategies. Requirements are the bridge between the usage analysis and solution description. A complete statement of requirements demonstrates that project team understands its customer’s needs. The statement also becomes the baseline for more detailed technical documentation in the planning phase. Good requirements analysis lowers the risk of downstream surprises.>

Information described in the following sections defines business, functional, operational and technical requirements that must be met for the Datacenter Infrastructure and Management engagement to be successful.

3.4 Business RequirementsThe Datacenter Infrastructure and Management solution offering should provide [Customer] with a Datacenter Infrastructure and Management solution featuring:

Integrated and consolidated Infrastructure Management capability, including management of heterogeneous environment, abstraction of infrastructure resources and in-depth performance and fault management capability

Improved SLA and service availability through end-to-end IT service monitoring and recovery Risk mitigation through process optimization and service deployment standardization

Process improvement through automation and decomposition of key processes and activities.

3.5 Functional RequirementsThe Datacenter Infrastructure and Management solution offering solution should satisfy following functional requirements:

End-to-end performance and fault management of the heterogeneous IT environment (infrastructure) Seamless integration with existing IT management systems Extensive knowledge base for managed infrastructure, including full health model and customized

operations monitoring of the scoped environment Full management capabilities across physical and virtualized resources Abstraction of the key infrastructure resources (compute, network, storage and virtualization) in order to

simplify resource provisioning and augment functional capabilities Deep application monitoring and management, enabling advanced and efficient troubleshooting, as well as

improved cross-group collaboration between Technical and Application Management functions

End-to-end service monitoring, performance and fault management through advanced infrastructure and application management functionalities.

3.6 Operational RequirementsThis offering utilizes an Infrastructure-as-a-Service (IaaS) Product Line Architecture (PLA). This PLA includes patterns which have been identified for the development of a private cloud infrastructure based on Windows Server 2012 R2 and System Center 2012 R2. By implementing private cloud configurations built on the IaaS PLA, the Datacenter Infrastructure and Management offering provides organizations both the control and the flexibility that are required



to reap the potential benefits of private cloud. Datacenter Infrastructure and Management solution should fulfill following operational requirements:

<Capture customer specific requirements. Samples provided below.>

Development of a managed private cloud infrastructure Development of a management capability capable of managing on-premise and public cloud IaaS

infrastructures Physical and virtual machine provisioning

Enabling patch management of a private cloud environment without impact to running workloads.

3.7 Technical Requirements<Technical requirements section should focus on some key technical aspects of the implemented solution including hardware and software standards, security and continuity guidelines, system integration and overall architecture guidance. These requirements are dependent on the customer’s overall architecture and should be developed and aligned with customer’s technical architecture, models and standards.>

<Example follows.>

The Datacenter Infrastructure and Management solution delivered through this project should fulfill following technical requirements:

All components should include out-of-the-box connection, catering for integrated and unified solution architecture

The solution should offer standardized and well-documented APIs or Web Services allowing simplified integration toward other systems and expansions in-line with possible future requirements

The solution should be able to utilize customer’s standard corporate central database system leveraging SQL Server technology

The solution should include advanced role-based management capabilities, leveraging existing Identity and Management solution, already available in the IT environment

All virtual machine and service templates should be customizable and adaptable to the changing business needs

The solution should provide management capabilities across multiple hypervisor technologies from Microsoft, Citrix and VMWare.



4 Scope of the Project< This chapter should introduce and discuss overall scope of the project. Information should be kept at the visionary and conceptual level, referring to the Scope of Work document for detailed decomposition of the project’s scope and contractual obligations. >

The project team will take an iterative and architectural approach throughout envisioning and planning of the engagement, working with [Customer] to identify and investigate business requirements and develop a set of architectural and technical functional requirements that will in the end produce the specific solution architecture, deployment structure and project scope.

The project scope includes all activities needed to envision, plan, build, test, stabilize and deploy the Datacenter Infrastructure and Management solution, leveraging Microsoft Solutions Framework (MSF) engagement model. Depending on the project’s overall complexity, engagement could feature multiple iterative phases or even apply agile methodology in order to accelerate progress and provide greater value to the [Customer].

4.1 Project Objectives< Objectives are divided into business and technical objectives and based on the outcomes and findings of the presales activities and Solution Definition Workshop. These objectives will serve as an input into relevant Decision Leading Workshop and cascade into detailed Scope of Work which will accompany adequate contractual documentation. >

4.1.1 Business Objectives< This subchapter lists project’s key business objectives. Keep the section brief and use bulleted form. Leverage “Business Opportunity”, “Benefit Analysis” and “Project Requirements” content to compile a concise but relevant list of business objectives. >

The Datacenter Infrastructure and Management solution envisioned and scoped for the [Customer] is aiming to fulfill following key business objectives:

Improve availability, stability and predictability of the IT ecosystem through consolidated, holistic and integrated IT management capability, reducing risk and directly impacting business value of key IT services delivered to business

Increase agility of the IT function allowing for faster and targeted response to business needs and changing market conditions

Greatly improve SLA value and end-to-end availability of key IT services through reduced service downtime, improved performance and fast restore capabilities on a private cloud infrastructure

Provide end-users with self-service capability, allowing them to tailor their IT experience, while having full control of the service price and content.



4.1.2 Technical Objectives< This subchapter lists project’s key technical objectives. Keep the section brief and use bulleted form. Leverage “Business Opportunity”, “Benefit Analysis” and “Project Requirements” content to compile a concise but relevant list of business objectives. Note that technical objective will typically evolve around management consolidation, integrated management capabilities, fast incident response, advanced troubleshooting, optimization of the key IT processes, cross-group collaboration and heterogeneous management capacities. >

The Datacenter Infrastructure and Management solution envisioned and scoped for the [Customer] is aiming to fulfill following key technical objectives:

Build consolidated and integrated IT management system capable of providing holistic and end-to-end control and visibility across heterogeneous and complex IT ecosystem.

Consolidated management of a private cloud infrastructure Increase agility of the IT function allowing for faster and targeted response to business needs and

changing market conditions Greatly improve SLA value and end-to-end availability of key IT services through reduced service

downtime, improved performance and fast restore capabilities on a private cloud infrastructure

Provide end-users with self-service capability, allowing them to tailor their IT experience, while having full control of the service price and content.

4.2 Scope< Scope of the Projects section is divided into two sub-chapters, clearly specifying what is included and what is excluded from the engagement’s scope. It is strongly recommended to keep the scope language concise, brief, specific and in bulleted form. Please refrain from using marketing or business terminology and focus on the will be delivered, both in terms of activities and specific deliverables. Cover all phases, aspects and details of the project, creating a strong baseline based on the Statement of Work and remaining contract documentation. >

4.2.1 In Scope< In scope sub-chapter lists key activities and deliverables that are included in the engagement’s scope and that will be addressed through the actions of the project team. Listed activities and deliverable present a draft model of the typical engagement. Please modify and contract/expand in accordance with specific needs, characteristics and goals of the particular project. >

The Datacenter Infrastructure and Management solution offering will assist with the planning, building, stabilizing and deployment of a Microsoft Private Cloud infrastructure based on the Windows Server 2012 R2 and System Center 2012 R2 platforms. Included are the following services:

Requirements gathering Use case analysis Development of test scenarios as outlined in this document Development of a vision and scope document/objective Assistance with dependent architectural preparation (Active Directory, DNS, DHCP, PXE, Windows Deployment

Services, Compute, Network and Storage)



Assistance with environment and validation testingo Server, storage, network validationo Assistance with the configuration and deployment of the Windows Server 2012 R2 platform

A Windows Server 2012 R2 and System Center 2012 R2 private cloud functional specification for the planned environment including

o Deployment for Hyper-V role, and other related roles on Windows Server 2012 R2o Deployment of System Center 2012 R2; including the following System Center components:

Virtual Machine Manager (VMM) Operations Manager (OM) Service Manager (SM) App Controller Orchestrator

o Deployment of the Windows Azure Pack

Support automated virtual machine (VM) provisioning using out-of-the-box functionality of System Center 2012 R2 and a simple Virtual Machine Manager (VMM) service template consisting of Windows Server 2012 R2 roles.

4.2.2 Out of Scope< Content of the Out of scope sub-chapter will heavily depend on the relationship with the customer, quality of the Statement of Work and the estimation of the level of detail appropriate for the project. It could be an extensive chapter if Engagement and/or Project Manager assess that project is risky and faces uncontrolled scope bloat. Out of Scope and In Scope sub-chapters are in oppositely proportional – extensive and detailed In Scope content will significantly reduce the size of Out of Scope content. Use clear, specific and bulleted form. Example below should be used as the reference only and modified in accordance with specific needs, characteristics and goals of the particular project. >

< Example follows. >

The following capabilities and functionalities are outside of the proposed/agreed Datacenter Infrastructure and Management project for [Customer]. The areas that are out of scope for this engagement include, but are not limited to, the following:

Installation of hardware (racks, servers, etc.) or sourcing or procurement of hardware and/or software Implementation or Integration of existing customer Microsoft, third-party and in-house developed products,

components or other solutions outside of the deployment of the Windows Server 2012 R2 Hyper-V and System Center 2012 R2 environment.

Deployment of System Center components outside of those identified as in-scope Customization outside of that which can be configured within the in box graphical user interfaces of the

products Windows Server operating system custom image design or configuration outside of the creation of a

sysprepped virtual machine image for Virtual Machine Manager deployment Workload application compatibility, custom application remediation or configuration or integration of

workloads, Microsoft or 3rd party Building and conducting end-user training classes and materials Physical to Virtual or Virtual to Virtual Migration



Customer certification and accreditation activities outside of general support for customer processes No data migration is included in the scope of this statement of work. Ownership of artifacts for customer

change management processes Operating or maintaining [Customer]’s systems Creation or maintenance of customized Orchestrator workflows as part of the deployment Creation or maintenance of an operating system image Detailed design and formal review of Project Work Products Setup or configuration of any other environments.

4.3 Acceptance Criteria<Define the metrics that must be met for the customer to understand that the solution meets its requirements. Make sure metric conform to the S.M.A.R.T. concept and fully integrated with project’s scope and objectives. >

Why: Acceptance criteria communicate to the project team the terms and conditions under which the customer will accept the solution. Successful acceptance test will also determine project’s closure and (depending on the payment and revenue recognition terms) could significantly affect financial performance of the project contractor(s).

Following Acceptance criteria example provides a draft view into possible acceptance metrics. Please make sure you thoroughly discuss real acceptance criteria during project’s envisioning and scoping and modify the list below with relevant and appropriate metrics. Acceptance criteria can combine business and technical objectives, operational aspects, performance metric and even financial goals. Regardless of the criteria’s origin they should be SMART, relevant and final. >


Based on the mutual agreement of <Partner name>Microsoft Services and [Customer], the following jointly agreed upon acceptance criteria for this Datacenter Infrastructure and Management project:

Average virtual machine provisioning time reduced below X minutes, measured during second and third month after solution’s production

Ability to manage and monitor Hyper-V, VMWare and Citrix hypervisor, measured through demonstration of the VM provisioning on the production system

Ability to intelligently patch managed cluster, without virtualized workload downtime, measured through demonstration of the patching process on the deployed Private Cloud system.

4.4 Operational Critieria<Define the conditions and circumstances by which the customer’s operations teams judge the solution ready to deploy into the production environment. Once deployed, the customer takes ownership of the solution. This section may specify the customer’s requirements for training operators and administrators, using the different elements of the deployed Datacenter Infrastructure and Management solution to manage scoped aspects of the IT Service Management lifecycle.

Why: Operational criteria communicate to the project team the terms and conditions under which the customer will allow deployment and ultimately sign off-on the project. While deployment solution could satisfy acceptance criteria



(which are focused on functional characteristics), operational criteria might prevent project completion since customer is not capable to apply and use the deployed solution in the everyday operational practice.

Operational criteria could be merged with Acceptance criteria and certain criteria could be found in both lists. >

<Example follows. >

Based on the mutual agreement of <Partner Name>Microsoft Services and [Customer], the following jointly agreed upon operational criteria for this Datacenter Infrastructure and Management project:

Average virtual machine provisioning time reduced below X minutes, measured during second and third month after solution’s production

Ability to manage and monitor Hyper-V, VMWare and Citrix hypervisor, measured through demonstration of the VM provisioning on the production system

Ability to intelligently patch managed cluster, without virtualized workload downtime, measured through demonstration of the patching process on the deployed Cloud infrastructure.



5 Risk Management< Risk management chapter of the Vision & Scope document typically presents the information from the project’s Risk Register. Compile the Risk Register content into following table and update as project progresses. Following list of risks presents the draft model – please modify and extend as appropriate. Use only “Possible Risks” and “Risk classification / category” columns from the Risk Register document. >


Possible risk Risk classification / categorization

<Identify risk statement> <Risk categories:>

People: customers, users, sponsors, stakeholders, personnel, organization, skills, politics, morale, availability

Process: missions and goals, decision making, project characteristics, budget / costs / schedules, requirements and objectives, designs, building, testing

Technology: security, development and test environment, tools, deployment, production environment, support, availability

Environment: legal, regulatory, competition, economic, technology, business

Lack of executive involvement and sponsorship to help address and manage obstacles as they arise

People: Sponsors, Stakeholders, Organization, Politics

Lack of executive and management involvement to help manage the organizational change associated with Datacenter Infrastructure and Management project

People: Sponsors, Stakeholders, Organization, People Management

Lack of development and testing environment that faithfully mirrors the production environment and meets the requirements set forward in the Vision & Scope document

People: Personnel, Skills

Process: Building, Testing

Technology: Development and Test Environment

Insufficient and inadequate solution testing before Stabilize




Possible risk Risk classification / categorization

and Deploy phases Process: Budget, Costs, and Schedules; Requirements

Technology: Development and Test Environment

Insufficient expertise with products and technologies such as System Center products, Microsoft Windows platform.


Lack of available or sufficient infrastructure (compute, storage, networking) for Datacenter Infrastructure and Management solution deployment

Technology: Deployment

Environment: Technology

Unexpected issues or technical challenges may necessitate a level of discovery that was not anticipated in initial scoping

Process: Budget, Costs, and Schedules; Testing Technology: Development and Test Environment, Tools, Deployment

Existing solutions have complex functionalities that have not been captured during assessment

Process: Requirements, Designs, Building, Testing

Technology: Tools, Development and Test Environment

Unavailability of the competent resource to address particular product or technology challenge



datacenter infrastructure and management - … · web vieworganizations today are demanding...

Documents