Skip to main content

Evaluate Dynamics 365 with a Proof of Concept



Choosing software is a big commitment, and you want to be sure that you don't regret your choice later.  One of the best ways to evaluate Microsoft Dynamics 365 and apps built on the Dynamics platform is to conduct a proof of concept.

Here are some of the keys to make your proof of concept (POC) successful:

  1. Set a schedule and stick to it. You need a predefined beginning and end to the proof of concept.  One month has been good for InfoStrat clients, allowing for requirements gathering, training users and tackling key functional challenges.  Don't let it drag out beyond the deadline.  
  2. Involve the right users. Find users who are willing to devote the necessary time to participate.  Consider who your key stakeholders are and make sure they are represented.
  3. Provide training and support for users. Don't turn users loose on a system without providing orientation, training and support during the POC.  Most business software is sufficiently complex that it is not reasonable to expect users to learn it on their own. 
  4. Define success criteria. The first step in the POC is to define the success criteria and write them down.  Make them as objective as you can in order to simplify evaluation. 
  5. Include time and format for evaluation. Once the POC has been running, facilitate evaluation sessions to evaluate how the solution meets business needs.  Online surveys with tools such as Dynamics itself or SharePoint can help you gather feedback from users. 
  6. Keep it a POC.  A proof of concept is not a complete implementation.  Help participants understand that not every requirement will be fulfilled.  If you set correct expectations you are less likely to disappoint users. 
Microsoft Dynamics lends itself to a POC because it is a cloud solution and you do not have to spend time installing or configuring on your servers.  You can sign up for a free trial which will give you enough time to run a POC if you are prepared with user requirements. 

Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do not require advan