sharepoint work order template · web viewsharepoint work order template. prepared for: customer...

SharePoint Work Order TemplatePrepared for:Customer NameNameTitle{Date}Version

Prepared by:Partner NameNameTitleMicrosoft Deployment Planning Services Partner

Microsoft Software Assurance SharePoint Deployment Planning Services

SharePoint Work Order Template

ContentObjectives........................................................................................................................................... 2Scope................................................................................................................................................... 2

Service Areas within Scope..........................................................................................................2Plan the Solution – SharePoint one (1) day engagement.......................................................2Plan the Solution – SharePoint Three (3) Day (non-upgrade) Engagement.........................3Plan the Solution – SharePoint Three (3) Day (upgrade) Engagement.................................3Plan the Solution – SharePoint Five (5) Day Engagement......................................................4Plan the Solution – SharePoint Ten (10) and Fifteen (15) Day Engagement.......................5

Service Areas Out of Scope..........................................................................................................6Approach............................................................................................................................................. 6

Key Partner Name Activities........................................................................................................6Key Customer Activities................................................................................................................6Key Service Deliverables..............................................................................................................7

Project Roles and Responsibilities...................................................................................................7Roles and Descriptions.................................................................................................................7General Customer Responsibilities and Project Assumptions..................................................8Project Assumptions......................................................................................................................8

1


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 Name and Customer Name are defined as Advanced Properties of this document. To modify them, go to File Properties Advanced Properties).

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

ScopeService Areas within ScopePartner 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 engagementThis 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

2


Plan the Solution – SharePoint Three (3) Day (non-upgrade) EngagementThe 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 stepsThe 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) EngagementThe engagement includes the following: SharePoint Overview Session – This session introduces the new features of SharePoint and the Office


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

3


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 stepsThe 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 EngagementPartner – 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


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

4


– 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 EngagementThis 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 EnvironmentSharePoint 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 ScopePartner – 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

5


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

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

Key Partner Name ActivitiesPartner – 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 ActivitiesPartner – 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

6


Key Service DeliverablesFollowing 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 ResponsibilitiesPartner – Revise as necessary.

Roles and DescriptionsRole Role DescriptionProject Manager 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

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

projectCustomer Technical Leads

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

Customer Project Sponsor

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 engagementCustomer Project Manager

Sign off on Project deliverable-specific documents

7


General Customer Responsibilities and Project AssumptionsPartner – Please customize and add or delete sections as appropriate for your engagement.The following are the responsibility of Customer Name Project management and assigning project manager or managers (“owners”) as needed, to specific

technical initiatives. Overall technical direction for customer IT infrastructure, and how it affects the Solution. Ensuring availability of any required hardware and software. Provision of workspace, including desk, phone with internal and external access, network connection,

print services, computer space, and an additional line (analog) for remote access to communicate with internal corporate network or virtual private network (VPN) access through customer’s corporate Internet connection.

Provision of access to customer’s facilities and systems while maintaining appropriate levels of security.

Provision of timely access to people, documentation, and systems as required for successfully implementing and completing this engagement.

Provision of clear goals and objectives mapped to customer’s business and IT strategies. Joint goals and objectives need to be created and reviewed on a project-by-project basis.

Provision of access to customer’s management and planners. To be successful, Partner Name team will need regular access to IT leadership to be able to provide input on customer’s strategic business and IT directions as they relate to the use of Microsoft products and technologies.

In addition to any customer activities identified elsewhere in this Work Order, Customer Name will perform or provide the following:Partner – Please describe specific Customer responsibilities.In performing our services under this work order and any applicable work order, we will rely upon any instructions, authorizations, approvals, or other information provided to us by your Project Manager or personnel duly designated by your Project Manager.

Project AssumptionsThe services, fees, and delivery schedule for this project are based upon the following assumptions: The availability of your representatives to perform their roles on the project team. The availability of all the information required for properly creating the project deliverables. Product licenses. Product licenses (Microsoft or non-Microsoft) will not be provided under this work

order. Customer is responsible for acquiring all necessary product licenses required as a result of this work order.

8

sharepoint work order template · web viewsharepoint work order template. prepared for: customer...

Documents