12
Implementing Microsoft Dynamics CRM Proof of Concept Project Close Out

10_Proof of Concept Project CloseOut Presentation_CRM.pptx

Embed Size (px)

DESCRIPTION

school

Citation preview

10 Proof of Concept (PoC) Project Close-out Presentation CRM

Implementing Microsoft Dynamics CRM

Proof of Concept Project Close Out

Agenda2Review objectivesReview engagement process flowPresent demonstration feedback and changesAcknowledgementsNext stepsQuestions and answers

The primary objectives of the Proof ofConcept were:Demonstrate Microsoft Dynamics CRM with your data and business processesBuild consensus around the proposed CRM solutionFurther understand your business requirementsValidate that Microsoft Dynamics CRM will work with your more complex business processesProvide an environment that enabled you to do further testing and user trainingProof of Concept Engagement Objectives3

Proof of Concept Engagement Process Flow4This is the process flow we used to deliver the conference room pilot. StartFinishSelect subset from Fit GapBuild in test environmentDemonstrate to BDM/ITDMs in one- to two-day workshopUpdate Fit Gap & Solution BlueprintPilot environmentActivities

This can be a flow diagram, illustration, table, or text that outlines the engagement steps or phases. Provide a high-level view of activities and milestones on this slide or the next if needed.

2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.9/10/20134

Proof of Concept Engagement Process Flow5This is the process flow we used to deliver the conference room pilot. StartFinishSelect subset from Fit GapBuild in test environmentDemonstrate to BDM/ITDMs in one- to two-day workshopUpdate Fit Gap & Solution BlueprintPilot environmentActivities

This can be a flow diagram, illustration, table, or text that outlines the engagement steps or phases. Provide a high-level view of activities and milestones on this slide or the next if needed.

2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.9/10/20135

The key feedback points uncovered during the demonstration of the Proof of Concept tothe business and IT decision makers(BDM/ITDMs) are:

Demonstration Feedback6

Fit Gap Changes7Based on changes arising from the Proof of Concept, the revised Fit Gap analysis has determined a % degree of fit for Microsoft Dynamics CRMThe revised effort estimates that have been developed are:Configuration =Customization = Workflow = Degree of Fit: Out of Box, Configuration, Customization, Workflow, ISV Add-on

2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.9/10/20137

Fit Gap Changes8Degree of Fit: Out of Box, Configuration, Customization, Workflow, ISV Add-onCustomization, 9%Workflow,2%3rd Party Add-On, 4%Std Features,46%Configuration, 39%Based on changes arising from the Proof of Concept, the revised Fit Gap analysis has determined a % degree of fit for Microsoft Dynamics CRMThe revised effort estimates that have been developed are:Configuration =Customization = Workflow =

2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.9/10/20138

The required changes identified during the demonstration of the Proof of Concept to the BDM/ITDMs are:

Solution Blueprint Changes9

Thank you to the following participants in this engagement:List customer and partner resources who aided the engagement Acknowledgements10

The proposed next steps are:Perform a scoping assessment to determine the overall implementation costs and resource planComplete a business case analysis, if requiredNext Steps11

Please ask any questions arising from this presentation.Questions and Answers12