SharePoint 2013 Engagement Findings and Recommendations Documentation

Document Sample
SharePoint 2013 Engagement Findings and Recommendations Documentation Powered By Docstoc
					Software Assurance Planning Services


Engagement
Findings and
Recommendations
[Header]




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



[Right-click on table of contents to UPDATE FIELD.]
[Again, DO NOT DELETE SECTION BREAK between the chosen table of content and the body of the document!]



[Step 2 - delete the 2 tables of contents you don't need. Make sure NON-PRINTING CHARACTERS are showing to remove the page breaks.]




Software Assurance | [INSERT DOCUMENT NAME]                                                                                                                                                                   i
Planning Services Engagement Findings and Recommendations


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.



 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.




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]



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


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]



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


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




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]




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


    Requirement Topic                               Requirement Detail

    [Upgrade]                                       [Detail]



2.3 High-Level Solution
This section outlines the high-level solution based on [Customer’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.




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


3.1 Conceptual Design
Based on the information gathered, the conceptual design of [Customer’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.

Example: Conceptual Design
                                                                                               Customer
                                                                                              Environment


                                                                        Solution
                                                                                               LOB Data
                                             Web
                                                                             Document
                                                                            Management


                                                                            Web Content       SQL Server
                                                               Search       Management
   Users
                                           Microsoft
                                          Office 2013
                                                                          Rights Management     Identity
                                                                                              Management




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




3.2 Logical Architecture
The Logical Architecture of [Customer’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.

  .




3.3 Physical
The Physical Architecture of [Customer’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.




4. Next steps
Based on the findings during this SDPS session, next steps would include:
         [Next Step]

         [Next Step]



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

       [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.



5. Customizations
The 5, 10, and 15-day engagements provide the opportunity to apply customizations to the base environment. This
section captures customizations that are applied to the environment. For a list of suggested customizations, please see the
SharePoint 2013 - Scenarios Walkthrough. It should be noted that you are not limited to the customizations listed in the
document.

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


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




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




                  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 you’d 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.




Software Assurance | SharePoint Deployment Planning Services                                                     7

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:6
posted:2/24/2013
language:English
pages:9