Software Assurance Planning Services

Engagement
Findings and
Recommendations


[Header]
Software Assurance | [INSERT DOCUMENT NAME] i
Table of Contents
Introduction ............................................................................................................................................................................................ 1
1. Strategy Briefing Session Summary ............................................................................................................................... 1
2. Envisioning Workshop Summary .................................................................................................................................... 3
3. Design Considerations ........................................................................................................................................................ 4
4. Next steps ................................................................................................................................................................................ 5
5. Customizations .......................................................................................................................................................................... 6



Planning Services Engagement Findings and Recommendations
Software Assurance | SharePoint Deployment Planning Services 1

Introduction
SharePoint Deployment Planning Service (SDPS) presents key concepts and captures environment requirements for the
deployment of Microsoft SharePoint 2013 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 2013 may be referred to as SharePoint 2013 ; however, when referring to the
environment as a whole, the term SharePoint is used. Microsoft SharePoint Foundation 2013 is referred to as SharePoint
Foundation.




1. 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 2013 capabilities, understanding the environment and developing a problem statement
that can be addressed by SharePoint 2013 capabilities.
The following sections give a summary of the output of this session:

1.1 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]

1.2 Business Goals
[Customer] has the following business goals that were identified during this session:
[Business Goal 1]
[Business Goal 2]
[Business Goal 3]
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 brackets and should be removed before you submit this document to Microsoft and your
Customer.
Planning Services Engagement Findings and Recommendations
Software Assurance | SharePoint Deployment Planning Services 2

1.3 Business Problem Statement(s)
The following business problem statement(s) were agreed to by session participants:
[Business Problem Statement]
[Business Problem Statement]

1.4 Business Solution Statement(s)
The following business solution statement(s) were agreed to by session participants:
[Business Solution Statement]
[Business Solution Statement]

1.5 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]

1.6 SharePoint 2013 Business Services Required
The session highlighted the following SharePoint 2013 capabilities and features that would enable [Customer] to achieve
their Business Goals.
Capabilities Features / Business Services
[Example: Search] [Example: Hybrid]
[Capability] [Feature]
[Capability] [Feature]
[Capability] [Feature]
[Capability] [Feature]

1.7 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]
Planning Services Engagement Findings and Recommendations
Software Assurance | SharePoint Deployment Planning Services 3

1.8 Next Steps
The following next steps were identified during this session:
[Step 1]
[Step 2]
[Step 3]



2. 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.

2.1 Deployment Challenges
The following key deployment challenges were identified during the session:
[Challenge1]
[Challenge2]
[Challenge3]

2.2 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 Mangment] [Detail]
[Customizations] [Detail]
[Search] [Detail]
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.
Planning Services Engagement Findings and Recommendations
Software Assurance | SharePoint Deployment Planning Services 4
Requirement Topic Requirement Detail
[Upgrade] [Detail]

2.3 High-Level Solution
This section outlines the high-level solution based on [Customers] solution requirements and deployment challenges.



3. Design Considerations

3.1 Conceptual Design
Based on the information gathered, the conceptual design of [Customers] solution can be illustrated as:

Example: Conceptual Design
Web
Users
Solution
Microsoft
Office 2013
Search
Document
Management
Web Content
Management
LOB Data
SQL Server
Identity
Management
Customer
Environment
Rights Management

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.

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 customers
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.
Consultants: Consider including the following information in Conceptual Design illustrations:
Users/Actors (persons and/or systems); Products required; SharePoint business services required, etc.

Planning Services Engagement Findings and Recommendations
Software Assurance | SharePoint Deployment Planning Services 5





3.2 Logical Architecture
The Logical Architecture of [Customers] solution can be illustrated as:




3.3 Physical
The Physical Architecture of [Customers] solution can be illustrated as:


4. Next steps
Based on the findings during this SDPS session, next steps would include:
[Next Step]
[Next Step]
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.

.

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.


Planning Services Engagement Findings and Recommendations
Software Assurance | SharePoint Deployment Planning Services 6
[Next Step]
[Next Step]
[Next Step]

5. Customizations
SDPS engagments are engineered for 3 to 5 day engagments and in some cases may be extened 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.
5.1 Summary of Customizations Implemented

5.2 Detailed Description of Customizations

[Customization 1]
[Customization 2]

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.

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.

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.

Planning Services Engagement Findings and Recommendations
Software Assurance | SharePoint Deployment Planning Services 7

THE USE OF QUICK PARTS
This template uses Quick Parts and Building Blocks extensively to store various elements
of this document Internal- and external-facing covers, three table of content options,
tables which hold both images and their corresponding captions, data tables, and
sidebars. All of these elements display thumbnails in the Quick Parts gallery so that you
can easily find what you need. (Insert ribbon, Text group, Quick Parts drop-down, Building
Blocks Organizer, click Name to bring WWLP elements to top of list.)
So, if youd like to use another color palette for your covers, delete ALL the covers in the
document, leaving the section break between the covers and the table of contents in
place. Your cursor should rest at the top of the first page. Then peruse your options in the
Quick Parts gallery.