Our enterprise architect, John Lomnicki, notified us this week that our use of Microsoft CRM has been published as a case study by Microsoft. That is exciting to me. It’s fun to read the article and realize what good work we are doing. Our CRM team is very small and our company is a non-profit. So I don’t think of us as special. But we are a dedicated group who work hard applying modern technologies to serve our customers.
Readers of this blog will enjoy knowing that I and the other CRM programmer use Microsoft Code Contracts to help improve the reliability, maintainability, recoverability, and overall quality of the custom code portion of this solution. I wrote previouslyhttps://codecontracts.info/2009/12/18/code-contracts-improve-microsoft-crm-workflow-code-2/ about the exact way in which we apply code contracts to detect and prevent faults, and resolve them more quickly when they do happen.
Here is the E-Mail from John, with a link to the case study.
From: John Lomnicki
Sent: Tuesday, January 12, 2010 9:27 AM
To: #All-Information Solutions
Subject: ELCA Board of Pensions XRM/CRM Case Study Published at Microsoft Site
The XRM/CRM Case study has been published out on the Microsoft website. It highlights our use of CRM as an XRM development platform for our organization. Many XRM implementations will build one or two XRM modules on top of CRM. Our organizational approach to collaboration allows us to use to use CRM Contacts and CRM Accounts as glue for up to 12 XRM modules that align nicely with our strategic plan objectives.
Why the case study is important for Microsoft
Microsoft’s strategic push around cloud computing involves bringing new features in the cloud. By leveraging the Dynamics CRM product as a XRM (extended relationship management) platform in the cloud organizations can build line of business applications without the burden of application infrastructure. CRM implementations that push the XRM boundaries of CRM help Microsoft deliver on their stated strategic objective.
What is XRM?
There are a couple of different definitions for XRM. One is that the “x” stands for extended, as in extended relationship management. The other definition is that the “x” is a variable, and means “anything” relationship management, such as partner relationship management, constituent relationship management, employee relationship management, etc. Both of these definitions are referring to building any application on top of the Microsoft Dynamics CRM platform. Building an XRM application can take the form of customizing the existing customer relationship management applications that are included in Microsoft Dynamics CRM, or by designing completely new line-of-business applications that are not based on the sales, service, or marketing capabilities included in Microsoft Dynamics CRM. The common thread to all the definitions of XRM and methods of extending it is that your application will use the Microsoft Dynamics CRM as a platform, leveraging the capabilities of the platform to deliver business value to your users. (more)
ELCA – Board of Pensions