Skip to main content

Estimating the Cost of Dynamics CRM Implementations: Part 8 -- Future Enhancements

This is the latest installment of ruminations on cost estimating for Dynamics CRM projects. Now that your xRM solution is in place and you have determined what kind of support you need to keep it alive, is that all there is?

For some customers, maintenance is the last item that requires professional services.   But building a software solution isn't usually like building a stone obelisk and placing it in the middle of your piazza.  For most people, it's more like planting a garden, and will require not only tending but will evolve over time based on which plants thrive.

The future may bring changes that require modifications to the solution.  Government agencies must ensure that their policies and procedures are consistent with laws and regulations which are constantly changing.   This regulatory compliance is not optional.

What if you come up with an improved business process and want to reflect it in your CRM solution?   Such changes could affect the data model, automated workflows and reports.  

In order to control the cost and disruptions of change, you may want to set up a release schedule to set expectations of users who request enhancements.    Over the course of an implementation you may move to less frequent releases. 

Don't forget that changes require notifications to users and sometimes refresher training.   A mechanism to solicit user feedback can identify ways to improve and boost user satisfaction at the same time. 


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