Engagement Findings and Recommendations

Engagement Findings and
Recommendations
Prepared for:
Prepared by
Customer Name
Partner Name
Customer Name
Name
Customer Title
Title
{Date}
Mobile Productivity
Version
Deployment Planning Services Partner
Engagement Findings and Recommendations
Table of Contents
Executive Summary .......................................................................................................................................................................... 3
Introduction......................................................................................................................................................................................... 4
Engagement Summary.................................................................................................................................................................... 5
Session Participant Record..................................................................................................................................................... 5
Project Stakeholders ................................................................................................................................................................. 5
Project Decision Making Process......................................................................................................................................... 5
Business Goals ............................................................................................................................................................................ 5
Business Problem Statements............................................................................................................................................... 5
Business Solution Statements ............................................................................................................................................... 5
1
Engagement Findings and Recommendations
INTERNAL: How to use this Template
DELETE this section before publishing
Tips to save yourself time, please read the following before starting to work in this template.
FORMATTING CONSIDERATIONS
Non-printing characters: Click the Show/Hide button (
what’s going on “behind the scenes.”
) located on the Home ribbon, Paragraph group to see exactly
View Gridlines: Use this setting to see the table gridlines so that you don’t accidentally click and drag them. (Layout tab,
Table group, View Gridlines button)
Styles: It is recommended to apply styles with the Styles panel (ALT+CTRL+SHFT+S) with Show Preview selected, but the
styles are also available on the Home ribbon. Do not apply any styling other than those listed.
PDF generation: In order to have crisp, clear logos and images in the final PDF, it’s important that PDFs be created in
Adobe Acrobat as “High Quality Print,” rather than the “Standard” setting that is built into MS Word. This setting is
available in Adobe Acrobat (Standard or Professional), which can be purchased separately if it’s not already installed on
your system.
New Visual Identity guidelines require Segoe Pro Font, which you can download from Media Bank. To
install the Segoe Pro font onto your computer, extract and open the folder. Copy the files inside that folder into
your fonts folder. Your fonts folder is located at C:\WINDOWS\Fonts. Need to reboot for them to appear in
your applications.
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.)
2
Engagement Findings and Recommendations
Executive Summary
Summarize the key outputs of the workshop and your recommendations
3
Engagement Findings and Recommendations
Introduction
Completed portions of this document serve as the deliverable required by Microsoft to pay for your services.
Guidance sections (such as this) are highlighted in yellow and should be removed before you submit this
document to Microsoft and your Customer.
Mobile Productivity Deployment Planning Services is designed to help you understand how an activated office for mobile application
can help deliver productivity benefits to your business. This document provides a summary of the topics discussed during the
engagement, as well as the vision and recommended next steps for deployment.
This [1 day/3 day] workshop is mainly focused on:

Giving an overview of the capabilities of Office for Mobile and includes out of the box capabilities of the mobile applications,
extensibility scenarios to connect the Office applications to LOB applications, and last but not least protecting and managing
corporate data being stored on employee devices.

Understanding your environment and identifying areas where the capabilities demonstrated could be used to solve a business
problem or scenario.

Helping you create an appropriate Office for Mobile deployment plan based on identified requirements and business
requirements.
Engagements longer than 3 days will also allow the customer to experience (via a POC solution built by the partner) how Office Add-ins
and Enterprise Mobility Suite could be used to address one of the business problems identified in the three day workshops. Please
describe the proof of concept(s) carried out as well as the outcomes that were achieved from it at the end of this document.
4
Engagement Findings and Recommendations
Engagement Summary
Session Participant Record
The following table summarizes the participants in this engagement and their expectations.
Name
Role
Expectations
[Name 1]
[Role]
[Expectation]
[Name 2]
[Role]
[Expectation]
[Name 3]
[Role]
[Expectation]
Project Stakeholders
The following table summarizes the project stakeholders that were identified.
Name
Role
Stakeholder Type
[Name 1]
[Role]
[Stakeholder/Influencer/Informed]
[Name 2]
[Role]
[Stakeholder/Influencer/Informed]
[Name 3]
[Role]
[Stakeholder/Influencer/Informed]
Project Decision Making Process
Describe the decision making process for the project as agreed by session participants
Business Goals
The following business goals that were identified during this session:

[Business Goal 1]

[Business Goal 2]

[Business Goal 3]
Business Problem Statements
The following business problem statement(s) were agreed to by session participants:

[Business Problem Statement 1]

[Business Problem Statement 2]

[Business Problem Statement 3]
Business Solution Statements
The following business solution statement(s) were agreed to by session participants:

[Business Solution Statement 1]
5
Engagement Findings and Recommendations

[Business Solution Statement 2]

[Business Solution Statement 3]
Office for Mobile Capabilities Required
The session highlighted the following Office for Mobile capabilities and features that would enable [Customer] to achieve their Business
Goals and/or helps solve the identified business problem and solution statements.
Capabilities
Stakeholder Type
[Example: Integrate Excel Application with SAP]
[Example: Office Add-in]
[Example: Encrypt corporate data stored on employee’s mobile devices]
[Example: Azure RMS]
[Example: Remotely wipe corporate data stored on employee’s mobile devices]
[Example: MDM for Office 365]
[Example: Require employees to have a secure pin on their mobile devices before
accessing corporate data]
[Example: MDM for Office 365]
[Example: Prevent employees from copy and pasting corporate data from office into
a personal app like twitter]
[Example: Microsoft Intune]
Prioritized High Level Requirements
The following requirements were identified, agreed and prioritized by session participants in relation to the capabilities specified above.
By rating each requirement in relation to its value to the business and complexity in implementation, we are able to prioritize the
requirements and focus on ones that provides the best return on investment (i.e. the quick wins). This prioritization formula will help us
define the roadmap and next steps for the deployment project.
Quick Wins
High Value, Low
Complexity
Discretionary
High Value, Low
Complexity
Strategic
High Value, High
Complexity
Ignore
Low Value, High
Complexity
6
Engagement Findings and Recommendations
Requirement
Business Value
Complexity
[Requirement 1]
[High/Medium/Low]
[High/Medium/Low]
[Requirement 2]
[High/Medium/Low]
[High/Medium/Low]
[Requirement 3]
[High/Medium/Low]
[High/Medium/Low]
Deployment Challenges
The following key deployment challenges (business, project or technical) were identified during the session:

[Challenge 1]

[Challenge 2]

[Challenge 3]
Success Criteria
The following success criteria were agreed to by session participants:

[Challenge 1]

[Challenge 2]

[Challenge 3]
7
Engagement Findings and Recommendations
High Level Solution
This section outlines the high-level solution based on [Customer’s] requirements and deployment challenges.
Describe your high level solution design (use any diagrams necessary to describe the design e.g. physical,
logical)
8
Engagement Findings and Recommendations
Proof of Concept (POC) Activities
This section is only required for engagements that are longer than 3 days. Please remove if this section is not
relevant to your engagement length.
Mobile Productivity Deployment Planning Services engineered for 1 or 3 day engagements and in some cases may be extended to no
more than 15 days. Engagements longer than 3 days are frequently required to implement one or more proof of concept solutions to
allow the customer to experience how the mobile productivity servies could be used to solve one or more of their business problems as
well as address concerns they may have. This section captures the proof of concept scenarios or the activities conducted in the
extended engagements that are outside of the normal 3 day engagements.
Summary of POC Scenarios Implemented
Use this section to provide an overview of the customizations that have been applied to the environment. Include
reasoning as well as outcomes or business benefits achieved by each proof of concept scenario.
Detailed Description of POC Scenarios Implemented
Use this section to provide details on proof of concept activities implemented in the customer’s environment.
Consider including: changes performed in the environment, logical, physical or other diagrams that helps
describe each of the proof of concept scenario implemented.
[POC Scenario Name 1]
[POC Scenario Name 2]
9
Engagement Findings and Recommendations
Proposed Roadmap
This section outlines the high-level deployment roadmap agreed by session participants.
Insert the roadmap you have agreed in the workshop
Phase 1
Phase 2
Phase 3
10
Engagement Findings and Recommendations
Next Steps
Based on the findings during this engagement, the next steps would include:

[Next Step]

[Next Step]

[Next Step]
11