Delivery Reference Guide
For Use Only by VMware and VMware Solution Providers
Not a Customer Deliverable
Delivery Reference Guide
© 2024 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and
intellectual property laws. This product is covered by one or more patents listed at
http://www.vmware.com/download/patents.html.
VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other
jurisdictions. All other marks and names mentioned herein are trademarks of their respective companies.
VMware, Inc.
3401 Hillview Ave
Palo Alto, CA 94304
www.vmware.com
© 2024 VMware, Inc. All rights reserved.
Page 2 of 11
Delivery Reference Guide
Contents
Contents...............................................................................................................3
1. Document Purpose.......................................................................................4
1.1 Prescriptive Design Decisions.......................................................................................4
2. Using this Delivery Kit...................................................................................5
3. This Engagement..........................................................................................6
4. General Delivery Instructions.......................................................................7
4.1 Introductions................................................................................................................7
4.1.1 Workshop Data Collection.............................................................................................................................7
4.2 Overview of Solution Methodology Phases..................................................................7
4.2.1 Phase: Initiate...............................................................................................................................................7
4.2.2 Phase: Plan....................................................................................................................................................8
4.2.3 Phase: Assess................................................................................................................................................8
4.2.4 Phase: Design................................................................................................................................................8
4.2.5 Phase: Implement.........................................................................................................................................8
4.2.6 Phase: Knowledge Transfer...........................................................................................................................8
4.2.7 Phase: Adopt.................................................................................................................................................9
4.2.8 Phase: Close..................................................................................................................................................9
5. Program Governance Instructions..............................................................10
5.1 Introduction................................................................................................................10
5.2 Overview of Program Governance Phases..................................................................10
5.2.1 Program Definition Phase............................................................................................................................10
5.2.2 Program Delivery Phase..............................................................................................................................10
5.2.3 Program Closure Phase...............................................................................................................................10
5.3 Templates...................................................................................................................11
© 2024 VMware, Inc. All rights reserved.
Page 3 of 11
Delivery Reference Guide
1. Document Purpose
The Delivery Reference Guide document is a supporting reference for those individuals involved in the
delivery of Professional Services Solution Builder derived engagements.
This document contains reference information on the following topics:
General Delivery Guidance
Micro-Services Definitions
1.1 Prescriptive Design Decisions
Every microservice offered by Professional Services Engineering has a set of design decisions defined
that are considered Best Practice. Microservices related to products in the SDDC realm leverage VMware
Validated Design based design decisions. Design decisions relating to EUC products are derived from
EUC BU defined Best Practice and Field recognized Best Practice. The intent of these Design Decisions is
to provide you the consultant guidance on the recommended configuration for a given products design.
Individual customer engagements may deviate from these Best Practices, and that is expected, but these
decisions form a baseline for you to work from.
© 2024 VMware, Inc. All rights reserved.
Page 4 of 11
Delivery Reference Guide
2. Using this Delivery Kit
The Engagement Delivery Kit is comprised of a few key set of Folders shown in the image below
The Engagement Details Folder, Solution Folder and Technology Folder each have documents that will
support the delivery. The EngagementWBS and EngagementWBS-for-MSProject each provide you will
the work breakdown of the engagement with every task, role assigned to the task and the effort
associated with each role. The EngagementWBS-for-MSProject can be imported into Microsoft Project
and provides the full GANT chart.
The edm-generation.log file is for diagnostic purposes if there have been issues in the generation of this
Delivery Kit.
The Engagement Details folder contains copies of the Service Scope and Description document that was
generated for this engagement. So that you can familiarize yourself with the scope of the engagement.
The Solution Folder contains the actual deliverables for this engagement. These deliverables have been
constructed by Solution Builder to be specific to the products and scope of this engagement and should
act as a good starting point for your engagement.
The Technology folder contains supporting materials, this could include the Visio diagrams file for the
respective products, and any tools provides by Professional Services Engineering.
© 2024 VMware, Inc. All rights reserved.
Page 5 of 11
Delivery Reference Guide
3. This Engagement
This section is a reference of the microservices in this specific engagement. This will advise you on items
like:
How to deliver the microservice
If a Workshop is involved, what information is important
What are the known risks associated with:
o This microservice
o The product relating to this microservice
Links to any known KB articles that are relevant to this microservice and product.
© 2024 VMware, Inc. All rights reserved.
Page 6 of 11
Delivery Reference Guide
4. General Delivery Instructions
This section provides detailed instructions on how to deliver any engagement effectively.
4.1 Introductions
To gain an appreciation of your audience:
Have a self-introduction of all the participants.
Introduce yourself and highlight your VMware expertise.
Ask for everyone’s name, email address and role.
Ask each participant why they are attending and what they expect to achieve from the
discussions.
Understand the overall project direction and timeline. This understanding is useful in determining
what the customer requires for a successful deployment.
The solution engagement begins with a focus on terminology and an overview. Although all
participants are encouraged to involve for the complete duration of the engagement, the
occasional curious onlookers, who need to understand only the high-level concepts (for example,
senior management), might participate only in the overview sections.
4.1.1 Workshop Data Collection
The section of this document that covers each of the microservices in your engagement will detail any
workshops. Make sure you are familiar with the workshop, you should have done the following before the
workshop:
Reviewed the workshop materials and potentially customized as needed
Reviewed the workshop section of the microservices in this document
Identified and understood the information you need to collect from the workshop
Understood how the information will be used in subsequent tasks of the engagement
4.2 Overview of Solution Methodology Phases
4.2.1 Phase: Initiate
VMware will conduct a pre-engagement planning call with to initiate the project. Topics to be discussed
include:
Review of project scope and objectives.
Project timelines, scheduling, and logistics.
Identification of key customer project team members with whom VMware will work to accomplish
the tasks defined in this SOW.
© 2024 VMware, Inc. All rights reserved.
Page 7 of 11
Delivery Reference Guide
Availability of appropriate facilities including, but not limited to, meeting rooms, work locations,
whiteboards, projectors, special access needs, any other pertinent information needed before the
VMware consultant arriving on site.
Prerequisites and other preparation required in advance for the project kick-off.
Security and access requirements.
4.2.2 Phase: Plan
The VMware engagement team will lead project sponsors and stakeholders in an engagement kickoff
meeting to review expectations about the purpose of the engagement, the delivery approach, and
timelines, the amount of time and effort required from the participants, expected schedule, activities and
work products. Meeting objectives include the following:
Introduce the VMware team, roles, and responsibilities.
Describe the project phases and agreement of key dates.
Agree on communication and reporting processes.
Validate the project expectations and clarifying roles and responsibilities.
Explain the expected project results.
Provide key stakeholders with the required terminology and knowledge to discuss and make
decisions throughout the design process.
Attendance by key representatives from the various teams is considered mandatory.
Refer to the product-specific knowledge transfer presentation kits for additional presentations.
Use the session to facilitate discussions and provoke thought.
Remind customer participants that the session is intended to give them a quick understanding of
the solution so that they can participate in the next phase (which covers design).
Keep a running list of questions and issues for consideration in the next phase.
End the session by discussing, defining, and scheduling the subsequent detailed requirements
gathering and design sessions.
4.2.3 Phase: Assess
The assess phase aims to identify the current state and determine the target state from a conceptual level
perspective. This phase aims to define the customer use cases.
4.2.4 Phase: Design
The design phase varies depending upon whether the micro-services involved in the specific customer
engagement and whether these micro-services are Design Class services or Extend Class services.
Extend Class services are focused on consumption of a technology platform; while Design Class services
are focused on the infrastructure perspective. The deliverable of this phase is the Solution Design
document.
© 2024 VMware, Inc. All rights reserved.
Page 8 of 11
Delivery Reference Guide
4.2.5 Phase: Implement
The implement phase includes the deployment of technology or process change based on the respective
components prescribed design. This phase also includes a functional test element; in this the consultant
implementing a component (process/technology) performs a functional test of the component to ensure
that at completion of this phase the component meets the requirement. The deliverables of this phase are
the Solution Specification Workbook and Verification Workbook.
4.2.6 Phase: Knowledge Transfer
This phase assists the customer with understanding the solution as a whole; this involves multiple
knowledge transfer workshops and partitioned content or a single workshop and content. The deliverable
of this phase is the Operational Guidelines framework document.
4.2.7 Phase: Adopt
This phase assists the customer with how to use the solution implemented, it follows the approach of see
one, do one and teach one. The Deliverable of this phase is the Adoption Guide document.
4.2.8 Phase: Close
The project review and conclusion activities include a final presentation that summarizes the engagement
activities performed for the resulting solution. A final set of deliverables will be provided to the customer.
© 2024 VMware, Inc. All rights reserved.
Page 9 of 11
Delivery Reference Guide
5. Program Governance Instructions
This section describes details that are applicable to large, complex or multi workstream projects as
specified by the program transformation office.
5.1 Introduction
The Program Transformation Office is a management structure that standardizes the program-related
governance processes and facilitates the sharing of resources, methodologies, tools, and techniques. The
VMware Program Director/Manager for a Program Transformation Office engagement will be engaged
right from the beginning and adapt to changes as required to support the overall business goals of the
program.
Many of these programs often run for long durations—multiple months and, in some cases, years.
Regardless of duration and workstreams, all programs follow a similar trajectory.
To successfully deliver benefits to a customer, programs are implemented using three major phases as
described below.
5.2 Overview of Program Governance Phases
This section discusses the three phases used as a part of this program.
5.2.1 Program Definition Phase
This phase consists of program activities conducted to understand and build a business case for the
delivery team to be engaged for the program and develop the program roadmap required to achieve the
expected results.
The program definition phase generally falls into two distinct but overlapping subphases as described
below.
5.2.1.1. Initiate
The primary purpose of the program initiation phase is to specify the goals and objectives to be
addressed by the program, define the expected program/business outcomes and benefits, and identify
the high-level risks and timelines associated with the goals.
5.2.1.2. Plan
In the plan phase a governance structure is established, the initial program organization is defined, and a
team is assembled to develop the program management plan that establishes the management control
and measures for controlling the performance.
5.2.2 Program Delivery Phase
Program delivery comprises the program activities performed to produce the intended results of each
project in accordance with the program management plan. Throughout this phase, individual projects are
initiated, planned, executed, transitioned, and closed, while benefits are delivered, transitioned, and
sustained.
© 2024 VMware, Inc. All rights reserved.
Page 10 of 11
Delivery Reference Guide
5.2.3 Program Closure Phase
This phase includes the program activities necessary to transition the program benefits to the customer
and formally close the program in a controlled manner. During program closure, the program is
transitioned and closed or terminated early, or work is transitioned to another program.
5.3 Templates
The templates for Program Governance can be downloaded from the folder below.
https://onevmw.sharepoint.com/:f:/r/sites/pse-solutions/PostSales/Program%20Governance
%20Templates
© 2024 VMware, Inc. All rights reserved.
Page 11 of 11
