Microsoft Software Assurance SharePoint Deployment Planning Services
SharePoint Engagement Findings and
Recommendations
Prepared for:
Prepared by
Customer Name
Partner Name
Name
Name
Title
Title
{Date}
Microsoft Deployment Planning Services Partner
Version
SharePoint Engagement Findings and Recommendations
Content
Introduction ............................................................................................................................................................................................................. 2
Strategy Briefing Session Summary .................................................................................................................................................... 2
Session Participant Record.................................................................................................................................................................... 2
Business Goals .............................................................................................................................................................................................. 2
Business Problem Statement(s) .......................................................................................................................................................... 2
Business Solution Statement(s) .......................................................................................................................................................... 3
Business Users Identified ....................................................................................................................................................................... 3
SharePoint 2013 Business Services Required ............................................................................................................................. 3
Products Required ..................................................................................................................................................................................... 3
Next Steps....................................................................................................................................................................................................... 3
Envisioning Workshop Summary.......................................................................................................................................................... 4
Deployment Challenges ......................................................................................................................................................................... 4
Solution Requirements ............................................................................................................................................................................ 4
High-Level Solution................................................................................................................................................................................... 4
Design Considerations ................................................................................................................................................................................ 4
Conceptual Design .................................................................................................................................................................................... 4
Logical Architecture .................................................................................................................................................................................. 5
Physical ............................................................................................................................................................................................................. 5
Next steps........................................................................................................................................................................................................... 6
Customizations ................................................................................................................................................................................................ 6
Summary of Customizations Implemented................................................................................................................................. 6
Detailed Description of Customizations ....................................................................................................................................... 6
1
SharePoint Engagement Findings and Recommendations
Introduction
SharePoint Deployment Planning Service (SDPS) presents key concepts and captures environment requirements for the
deployment of SharePoint within an organization. This document provides a summary of the topics discussed during the
engagement, as well as the vision and recommended next steps for deployment. In addition, any conceptual, logical, and
physical designs that were determined during the course of the engagement have been captured in this document.
In this document, Microsoft SharePoint may be referred to as SharePoint; however, when referring to the environment as a
whole, the term SharePoint is used. Microsoft SharePoint Foundation is referred to as SharePoint Foundation.
Consultants: Completed portions of this document serve as the deliverable required by Microsoft to pay for your services.
Guidance sections as well as sections to be filled in after each engagement day are marked with gray italics and should be
removed before you submit this document to Microsoft and your Customer.
Strategy Briefing Session Summary
The Strategy Briefing Session (SBS) comprises the first half of the one day SDPS engagement and is mainly focused on
giving an overview of SharePoint capabilities, understanding the environment and developing a problem statement that
can be addressed by SharePoint capabilities.
The following sections give a summary of the output of this session:
Session Participant Record
The following table summarizes the participants and their expectations.
Name
Role
Expectations
[Name1]
[Role]
[Expectation]
[Name2]
[Role]
[Expectation]
[Name4]
[Role]
[Expectation]
[Name5]
[Role]
[Expectation]
[Name6]
[Role]
[Expectation]
[Name7]
[Role]
[Expectation]
[Name8]
[Role]
[Expectation]
Business Goals
Customer Name has the following business goals that were identified during this session:
 [Business Goal 1]
 [Business Goal 2]
 [Business Goal 3]
Business Problem Statement(s)
The following business problem statement(s) were agreed to by session participants:
 [Business Problem Statement]
 [Business Problem Statement]
2
SharePoint Engagement Findings and Recommendations
Business Solution Statement(s)
The following business solution statement(s) were agreed to by session participants:
 [Business Solution Statement]
 [Business Solution Statement]
Business Users Identified
The following business users were agreed on by session participants:
 [Business User 1]
 [Business User 2]
 [Business User 3]
 [Business User 4]
SharePoint 2013 Business Services Required
The session highlighted the following SharePoint 2013 capabilities and features that would enable Customer Name to
achieve their Business Goals.
Capabilities
Features/Business Services
[Example: Search]
[Example: Hybrid]
[Capability]
[Feature]
[Capability]
[Feature]
[Capability]
[Feature]
[Capability]
[Feature]
Products Required
Based on the capabilities and features/business services required, the following IW products are needed to build the
solution:
 [Example: Office Professional 2013]
 [Product]
 [Product]
 [Product]
Next Steps
The following next steps were identified during this session:
 [Step 1]
 [Step 2]
 [Step 3]
Consultants: This concludes the deliverable sections required for a 1-day SDPS engagement. The following section begins
with the output from a 3-day SDPS engagement.
3
SharePoint Engagement Findings and Recommendations
Envisioning Workshop Summary
The Envisioning Workshop follows the Strategy Briefing Session and is part of the 3-day SDPS engagement. This session
mainly focused on identifying the requirements of collaboration, search, and enterprise content management.
Deployment Challenges
The following key deployment challenges were identified during the session:
 [Challenge1]
 [Challenge2]
 [Challenge3]
Solution Requirements
The following table summarizes the solution requirements based on the discussions held during this session.
Requirement Topic
Requirement Detail
[Platform]
[Detail]
[Social]
[Detail]
[Web Content Management]
[Detail]
[Customizations]
[Detail]
[Search]
[Detail]
[Upgrade]
[Detail]
High-Level Solution
This section outlines the high-level solution based on Customer Name’s solution requirements and deployment
challenges.
Consultants: Consider including the following information in the high-level solution description: solution statement; solution
requirements; SharePoint 2013 business services required; business users identified; desired end-state; etc.
Design Considerations
Consultants: At the end of a 3-day SDPS engagement you should be able to provide Conceptual Design, Logical and Physical
Architecture drawings that have been tailored to your customer’s environment. Guidance on preparing these deliverables is
included below. Please use these examples or provide your own alternate documentation of Conceptual Design, Logical and
Physical Architectures. These sections are required for payment.
Conceptual Design
Based on the information gathered, the conceptual design of Customer Name’s solution can be illustrated as:
Consultants: Consider including the following information in Conceptual Design illustrations: Users/Actors (persons and/or
systems); Products required; SharePoint business services required, etc.
4
SharePoint Engagement Findings and Recommendations
Example: Conceptual Design
Customer
Environment
Solution
LOB Data
Web
Document
Management
Search
Web Content
Management
SQL Server
Rights Management
Identity
Management
Users
Microsoft
Office 2013
Logical Architecture
The Logical Architecture of Customer Name’s solution can be illustrated as:
Consultants: Consider including the following information in Logical Architecture Illustrations: URLs for entry points (//portal,
//projects); classifications/taxonomies for site collections, etc.
Sample logical architectures can be found at:
http://technet.microsoft.com/en-US/sharepoint/fp123594
Note that in an upgrade scenario, you may wish to show both the current SharePoint 2010 architecture as well as the
proposed SharePoint 2013 architecture to facilitate comparisons. The above link hosts documents that can be used as
starting points for this approach.
Physical
The Physical Architecture of Customer Name’s solution can be illustrated as:
Consultants: Consider including the following information in Physical Architecture Illustrations: Domain names; Ports;
Application Pools; Server Names; IP Addresses; Passwords; Database Roles/Names, etc.
A physical architecture can be derived from the sample logical architectures described at:
http://technet.microsoft.com/en-US/sharepoint/fp123594
Note that in an upgrade scenario, you may wish to show both the current SharePoint 2007 architecture as well as the
proposed SharePoint 2010 architecture to facilitate comparisons. The above link hosts documents that can be used as
starting points for this approach.
5
SharePoint Engagement Findings and Recommendations
Next steps
Based on the findings during this SDPS session, next steps would include:
 [Next Step]
 [Next Step]
 [Next Step]
 [Next Step]
 [Next Step]
Consultants: This concludes the required deliverables for the 3-day SDPS Engagement. The following section begins with the
output of a 5-day SDPS Engagement.
Customizations
SDPS engagements are engineered for 3 to 5 day engagements and in some cases may be extended to no more than 15
days. Also, there are optional Proof of concept engagements that provide the opportunity to conduct scenario specific
engagements. This section captures the proof of concept scenarios or the activities conducted in the extended
engagements that are outside the normal 3 day engagements.
Summary of Customizations Implemented
Consultants: use this section to provide an overview of the customizations that have been applied to the environment.
Include reasoning and business benefits where applicable.
Detailed Description of Customizations
Consultants: use this section to provide details for any customizations. Consider including: style sheets/templates; coding
changes performed in the environment, logical diagrams of workflows, etc.
[Customization 1]
[Customization 2]
6