120 likes | 260 Views
Implementing Microsoft Dynamics CRM. Proof of Concept Project Close Out. Agenda. Review objectives Review engagement process flow Present demonstration feedback and changes Acknowledgements Next steps Questions and answers. Proof of Concept Engagement Objectives.
E N D
Implementing Microsoft Dynamics CRM Proof of Concept Project Close Out
Agenda • Review objectives • Review engagement process flow • Present demonstration feedback and changes • Acknowledgements • Next steps • Questions and answers
Proof of Concept Engagement Objectives The primary objectives of the Proof ofConcept were: • Demonstrate Microsoft Dynamics CRM with your data and business processes • Build consensus around the proposed CRM solution • Further understand your business requirements • Validate that Microsoft Dynamics CRM will work with your more complex business processes • Provide an environment that enabled you to do further testing and user training
Proof of Concept Engagement Process Flow This is the process flow we used to deliver the conference room pilot. Start Activities Select subset from Fit Gap Build in test environment Demonstrate to BDM/ITDMs in one- to two-day workshop Update Fit Gap & Solution Blueprint Pilot environment Finish
Proof of Concept Engagement Process Flow This is the process flow we used to deliver the conference room pilot. Start Activities Select subset from Fit Gap Build in test environment Demonstrate to BDM/ITDMs in one- to two-day workshop Update Fit Gap & Solution Blueprint Pilot environment Finish
Demonstration Feedback The key feedback points uncovered during the demonstration of the Proof of Concept tothe business and IT decision makers(BDM/ITDMs) are: • <insert feedback item 1> • <insert feedback item n>
Fit Gap Changes • Based on changes arising from the Proof of Concept, the revised Fit Gap analysis has determined a <insert percentage> % degree of fit for Microsoft Dynamics CRM • The revised effort estimates that have been developed are: • Configuration = • Customization = • Workflow = Degree of Fit: Out of Box, Configuration, Customization, Workflow, ISV Add-on
Fit Gap Changes • Based on changes arising from the Proof of Concept, the revised Fit Gap analysis has determined a <insert percentage> % degree of fit for Microsoft Dynamics CRM • The revised effort estimates that have been developed are: • Configuration = • Customization = • Workflow = Degree of Fit: Out of Box, Configuration, Customization, Workflow, ISV Add-on Customization, 9% Workflow,2% 3rd Party Add-On, 4% Std Features,46% Configuration, 39%
Solution Blueprint Changes The required changes identified during the demonstration of the Proof of Concept to the BDM/ITDMs are: • <insert Blueprint Change 1> • <insert Blueprint Change n>
Acknowledgements Thank you to the following participants in this engagement: • List customer and partner resources who aided the engagement
Next Steps The proposed next steps are: • Perform a scoping assessment to determine the overall implementation costs and resource plan • Complete a business case analysis, if required
Questions and Answers Please ask any questions arising from this presentation.