Business Solutions for Microsoft Dynamics CRM

xRM1 Pilot Implementation approach

Goals of the Pilot Implementation  Proof that the solution is the right decision  Being fast to show results  Keeping the end users enthusiastic  Stay low in efforts but get the security required  Provide an insight into future efforts for customizations and adaptations required

Benefits of a Pilot Implementation Security Actual usage of the software in one area Improved Processes The pilot project contains many best practises Low effort for the staff The software is in use live within 2 months Security in the processes On-the-Job coaching for staff Low implementation risk Fast and reliable implementation at a fixed price Implementation close to the standard Low follow-up costs after the implementation High value Experience of the manufacturer in the pilot implementation for an incredible price

Success factors for Pilot Implementation (DOs - People) People Choose people that are willing to change and discover Functionalities Focus on functionalities which enthuse people (close to their pain points, “nice” functionalities) Improvements Choose areas where managers and users are interested in making improvements Start thin Limit the number of users / process steps, but have relevant size (5-20 users best) Availability Choose people that are available (not on vacation, overworked,….) Support Provide the pilot team with professional support by experts knowing the solution inside out Schedule Get started fast

Success factors for Pilot Implementation (DOs - Functional) Functionalities Focus on functionalities which enthuse people (close to their pain points, “nice” functionalities) Current data Ensure some data are available for the pilot Processes Choose areas, where the to-be-processes are already well defined Infrastructure Ensure the technology works, is fast and users have access to the platform Standard Choose functionalities that are close to the standard of xRM 2011/2013

Success factors for Pilot Implementation (DON‘Ts) Technical restrictions Avoid current technical restrictions (network barriers, unavailable technologies) Approvals Avoid approvals that cannot be obtained on short notice Policies Avoid sensitive company policies Integrations Avoid integrations for the pilot No existing system Avoid double entry that drags motivation (Choose processes where no existing system is available) Extensive customizations Avoid extensive customizations / programming Requirement gathering Avoid extensive requirement gathering before the pilot