Sharepoint Work Order Template

Content

Objectives

Scope

Service Areas within Scope

Plan the Solution – SharePoint one (1) day engagement

Plan the Solution – SharePoint Three (3) Day (non-upgrade) Engagement

Plan the Solution – SharePoint Three (3) Day (upgrade) Engagement

Plan the Solution – SharePoint Five (5) Day Engagement

Plan the Solution – SharePoint Ten (10) and Fifteen (15) Day Engagement

Service Areas Out of Scope

Approach

Key Partner Name Activities

Key Customer Activities

Key Service Deliverables

Project Roles and Responsibilities

Roles and Descriptions

General Customer Responsibilities and Project Assumptions

Project Assumptions

Partner – Delete all pink text before you deliver this to the customer.

Use this template to define a Work Order format for your SharePoint Deployment Planning Services program.

Many partners will use their own Work Order templates, but for those who do not have one established, this will provide a benchmark for Work Order creation.(Note that Partner Nameand Customer Name are defined as Advanced Properties of this document. To modify them, go to File  Properties  Advanced Properties).

Objectives

Partner Name will provide the Microsoft® SharePoint Deployment Planning Services as described below.

SharePoint Deployment Planning Services (SDPS) is a value and deployment planning benefit available to eligible Microsoft® Volume Licensing customers with Software Assurance.SDPS consultants from Partner Name can help customers understand the value and best practices of implementing a Microsoft SharePoint Server solution in their on premise environment,.The number of SDPS engagement days varies from 1 to 15 as determined by their Software Assurance coverage and available days.

Any timelines, dates, and delivery schedules provided here are estimates only, and are subject to change.

Scope

Service Areas within Scope

Partner Name will provide the following services:

Partner – Choose 1 of the offerings below (1, 3, 5, 10 or 15 day engagement) and delete the rest. (There is a lot of repetition in the content across the offering descriptions.).

Plan the Solution – SharePoint one (1) day engagement

This one (1) day engagement includes delivering the SharePoint Overview presentation and discussions around the customer’s current SharePoint infrastructure.The main focus of the day will be to develop problem and solution statements (not architectures).The customer is provided with a simple deliverable that documents a problem statement, a solution statement, and next steps.

Note: Partners can substitute a different presentation on a more focused topic if required.This should be discussed with the customer as part of the pre-engagement call.

Details include:

• SharePoint Overview Session – This session introduces the new features of SharePoint and the Office 2013 client suite, and provides an overview of approaches for deployment. The discussion focuses on the business benefits of the new features and planning considerations for automating your deployment capabilities
• Problem Statement Development – This session acts as a high-level Envisioning Workshop, translating the business problem and solution statements into a high-level solution and summarizes how the solution could integrate with the customer’s environment.For the upgrade scenario, identify future value opportunities offered by SharePoint 2013, and capture any motivators the customer may currently have around proceeding with an upgrade to SharePoint 2013
• Summary and Roadmap Development – Based on the problem statement, this session presents the overall findings, including: business drivers, key deployment challenges, a proposed deployment strategy, high-level recommendations for further investigation, and next steps
  

Plan the Solution – SharePoint Three (3) Day (non-upgrade) Engagement

The engagement includes the following:

• SharePoint Overview Session – This session introduces the new features of SharePoint and the Office client suite, and provides an overview of approaches for deployment. The discussion focuses on the business benefits of the new features and planning considerations for automating your deployment capabilities
• Problem Statement Development – This session acts as a high-level Envisioning Workshop, translating the business problem and solution statements into a high-level solution and summarizes how the solution could integrate with the customer’s environment.For the upgrade scenario, identify future value opportunities offered by SharePoint , and capture any motivators the customer may currently have around proceeding with an upgrade to SharePoint
• Envisioning Workshops – Technical sessions covering a range of topics.These sessions introduce customers to the features and functionality of SharePoint Server and attempt to show how those features could be deployed to help meet the customers’ requirements.Topics to be covered typically include Search, ECM, Operational Readiness, Data Planning, and/or Infrastructure Planning, the exact sessions should be worked out in advance between the customer and the delivery consultant
• Creation of a Solution Concept – Based on the solution ideas that were derived from the various Envisioning Workshops, this session presents the solution concept.The solution concept is the initial step towards a solution design and is the starting point for future detailed design discussions.This solution concept IS NOT A FULL DESIGN and may not meet all Customer Name requirements
• Technical Drill Down – A detailed walk through of particular features in an out-of-the-box, pre-implemented SharePoint installation to show the customer particular features and capabilities of SharePoint in action.This SharePoint installation IS NOT A FULL INSTALLATION and will not meet all Customer Name requirements.
• Summary and Roadmap Development – Based on the problem statement, this session presents the overall findings, including: business drivers, key deployment challenges, a proposed deployment strategy, high-level recommendations for further investigation, and next steps

The final deliverable is a customized document that consists of the problem statement, any identified requirements, identified risks, a high level solution concept, and next steps

Plan the Solution – SharePoint Three (3) Day (upgrade) Engagement

The engagement includes the following:

• SharePoint Overview Session – This session introduces the new features of SharePoint and the Office client suite, and provides an overview of approaches for deployment. The discussion focuses on the business benefits of the new features and planning considerations for automating your deployment capabilities
• Problem Statement Development – This session acts as a high-level Envisioning Workshop, translating the business problem and solution statements into a high-level solution and summarizes how the solution could integrate with the customer’s environment.For the upgrade scenario, identify future value opportunities offered by SharePoint, and capture any motivators the customer may currently have around proceeding with an upgrade to SharePoint
• SharePoint Upgrade Overview Session – Includes various upgrade options and strategies
• Envisioning/Data-Gathering Workshops – Technical sessions covering a range of upgrade & migration topics.These sessions gather information on the customer’s use of features and functionality in SharePoint.Topics to be covered typically include Central Admin and SSP walk-throughs, Operational Readiness, Data Sources, Data Planning, Data Aggregation, and/or Infrastructure Analysis and Planning, the exact sessions should be worked out in advance between the customer and the delivery consultant
  
• Creation of a Solution Concept – Based on the solution ideas that were derived from the various Envisioning Workshops, this session presents the high level upgrade approach recommendation consisting of a list of activities that need to be pursued to better prepare for the ultimate upgrade future detailed design discussions.This upgrade approach recommendation IS NOT A FULL UPGRADE/MIGRATION PLAN and may not meet all Customer Name requirements
• Summary and Roadmap Development – Based on the problem statement, this session presents the overall findings, including: business drivers, key deployment challenges, a proposed deployment strategy, high-level recommendations for further investigation, and next steps

The final deliverable is a customized document that consists of the problem statement, any identified requirements, identified risks, the high level upgrade approach recommendation, and the next steps.

Plan the Solution – SharePoint Five (5) Day Engagement

Partner – If you choose to extend the engagement with optional days to conduct one of the program’s Proof of Concepts, modify the description immediately above and below to reflect the number of total days.

Adding optional days is considered an extensive engagement aimed at larger SharePoint organizations.It provides more time for deeper dives into SharePoint architecture, planning and deployment.

The engagement includes the following:

• SharePoint Overview Session – This session introduces the new features of SharePoint and the Office client suite, and provides an overview of approaches for deployment. The discussion focuses on the business benefits of the new features and planning considerations for automating your deployment capabilities
• Problem Statement Development – This session acts as a high-level Envisioning Workshop, translating the business problem and solution statements into a high-level solution and summarizes how the solution could integrate with the customer’s environment.For the upgrade scenario, identify future value opportunities offered by SharePoint , and capture any motivators the customer may currently have around proceeding with an upgrade to SharePoint
• Envisioning Workshops – Technical sessions covering a range of topics.These sessions introduce customers to the features and functionality of SharePoint Server and attempt to show how those features could be deployed to help meet the customers’ requirements.Topics to be covered typically include Search, ECM, Operational Readiness, Data Planning, and/or Infrastructure Planning, the exact sessions should be worked out in advance between the customer and the delivery consultant
• Creation of an Expanded Solution Concept – This is a more detailed description of the high level solution ideas that were derived from the various Envisioning Workshops.It should describe how product features could work together to solve the problem statement and meet the identified requirements. The solution concept is the initial step towards a solution design and is the starting point for future detailed design discussions.This solution concept IS NOT A FULL DESIGN and may not meet all of Customer Name requirements.The extended engagement allows time for expansion of the solution concept to include other items discussed as part of the technical presentations
• Conduct a POC (extended engagements only) – The POC is a tightly controlled, limited scope session using a temporary SharePoint tenant or deployment intended to show the customer particular features and capabilities of SharePoint in action. This POC SharePoint implementation IS NOT A FULL INSTALLATION and will not meet all Customer Name requirements

–Social Proof of Concept

–Enterprise Content Management Proof of Concept

–Search Proof of Concept

• Summary and Roadmap Development – Based on the problem statement, this session presents the overall findings, including: business drivers, key deployment challenges, a proposed deployment strategy, high-level recommendations for further investigation, and next steps.
• Custom Content Defined Jointly between Customer and Partner

–Custom objective 1

–Custom objective 2

Partner - Fill in the custom objectives…

The final deliverable is a customized document that consists of the problem and solution statements, any identified requirements, identified risks, an expanded high level solution concept, and next steps.

Plan the Solution – SharePoint Ten (10) and Fifteen (15) Day Engagement

This offering is an extensive engagement aimed at larger organizations by building on the five-day engagement. It provides time for deeper dives into SharePoint architecture, planning, and deployment. It is composed mainly of planning activities that can include tasks such as envisioning, requirements gathering, project planning, current state assessment, technical presentations, and labs.The primary focus and objectives of the deployment planning activities can be defined with the customer to better address their specific needs.

The ten-day and fifteen-day engagements are specifically designed to be customized and does not provide default predefined activities to fill each day. The specific planning activities and objectives for the remaining time are defined jointly between the consultant and the customer.

The final deliverable is a customized document that consists of the problem and solution statements, any identified requirements, identified risks, an expanded high-level solution concept, documentation of custom objectives and results, and next steps.

The engagement includes the following:

Strategy Briefing Session– Includes delivery of the SharePoint Overview presentation and creation of the problem statement.

Additional Time to review the Customer Environment

SharePoint Technical Presentations–Technical sessions covering a range of topics. These sessions introduce customers to the features and functionality of SharePoint and attempt to show how those features could be deployed to help meet the customers’ requirements. See the Construct Agenda section for more details.

Creation of an Expanded Solution Concept–This is a description of the high-level solution ideas that were derived from the various Architectural Design Sessions. It should describe how product features could work together to solve the problem statement and meet the identified requirements. The solution concept is the initial step towards a solution design and is the starting point for future detailed design discussions. This solution concept is not a full design and may not meet all of the customer’s requirements. The ten-day engagement allows time for expansion of the solution concept to include other items discussed as part of the additional technical presentations.

Custom Content to fill additional time.

Additional suggested content for ten-day engagements:

• Labs
• Project planning
• High level upgrade/co-existence concept planning
• Other custom content based on discussions with the customer

Service Areas Out of Scope

Partner – Using a bulleted list, identify specific areas that are out of scope for this engagement.Modify the content below as required.

Any area that is not explicitly listed as “within scope” is out of scope for this engagement. The areas that are out of scope for this engagement include, but are not limited to, the following:

• Microsoft Product Licenses
• Modifying and stabilizing the current server environment
• All network or server-related issues that need troubleshooting
• Installing any physical hardware
• Review of operational processes
• Industry regulatory compliance requirements

Approach

In this section, please include a description of the overall project approach, including Microsoft partner responsibilities, Customer responsibilities, and key deliverables.

Key Partner Name Activities

Partner – Customize the Partner Activities as appropriate.

• Lead the SharePoint Overview Session
• Lead the Envisioning Workshops
• Work with the customer to develop the solution concept
• Lead a detailed walk through of particular features in the customer’s lab environment
• Work with the customer to implement the proof of concept system (extended offering only)
• Work with the customer to implement the proof of concept system (extended offering only)
• Work with the customer to develop the final deliverable

Key Customer Activities

Partner – Please list activities that the Customer must accomplish during each phase, in addition to any prerequisites that must be accomplished prior to the beginning of the phase.

• Fill out and return the Pre-Engagement Questionnaire
• Work with the partner/delivery consultant on defining the program agenda
• Provide information on key business, operational, and technical requirements
• Provide input into the phases of the project covered by this Work Order and validating the results produced
• Schedule sessions to include appropriate personnel
• Attending sessions as appropriate
• Work with the delivery consultant to develop the solution concept (if applicable)
• Work with the delivery consultant to develop the final deliverable
  

Key Service Deliverables

Following is a list of key project mandatory service deliverables that will be delivered to the customer within this Work Order:

• Engagement Findings and Recommendations document - The content of this customer deliverable is the result of the Pre-Engagement Questionnaire and all activities during the engagement
• Delivery Evaluation Form

Partner – Please note that depending upon the length of the engagement the sections required for the Engagement Findings and Recommendations document will vary.See the “Customer Deliverable – Engagement Findings and Recommendations” section in the Microsoft SharePoint Deployment Planning Service Delivery Guide document for more information on the required sections by offering length.

Project Roles and Responsibilities

Partner – Revise as necessary.

Roles and Descriptions

• Responsible for stakeholder management, single point of contact to the customer for escalations, billing issues, contract extensions, project status, and overall engagement, financials, and risk management

• Responsible for delivering the engagement
• The Delivery Consultant provides technical oversight and leadership for all aspects of the project

• Assist delivery organization during discussions and meetings
• Provide input during discussions and meetings
• Have the ultimate responsibility for the project

• Ensure technical resources are available when needed
• Make key project decisions
• Assign key customer technical lead
• Responsible for review of delivery organization deliverables
• Sign off on scope for project
• Ensure facilities are available as needed
• Resolve critical-path issues in a timely manner
• Sign off on delivery organization documents and change control requests
• Accept and sign off in a timely manner on documents that pertain to the delivery organization Work Order, and which are critical to the success of the engagement

• Sign off on Project deliverable-specific documents

General Customer Responsibilities and Project Assumptions

Partner – Please customize and add or delete sections as appropriate for your engagement.