{"id":864,"date":"2014-06-15T17:04:21","date_gmt":"2014-06-15T16:04:21","guid":{"rendered":"http:\/\/blogs.encamina.com\/mascrm\/?p=864"},"modified":"2014-09-23T08:26:54","modified_gmt":"2014-09-23T07:26:54","slug":"auditing","status":"publish","type":"post","link":"https:\/\/blogs.encamina.com\/mascrm\/2014\/06\/15\/auditing\/","title":{"rendered":"Auditing a Microsoft Dynamics CRM system"},"content":{"rendered":"

What should I check in my CRM system to ensure it is performing as it should? Against which metrics should I check it to ensure it is alive and kicking?<\/span><\/p>\n

How should I audit my CRM system?<\/span><\/p><\/blockquote>\n

\"Audit\"

Audit<\/p><\/div><\/p>\n

This article is not about the ‘audit’ Dynamics CRM feature<\/a>. \u00a0Nor about\u00a0the consulting engagement on the ‘CRM’ strategy of a given organization.<\/span><\/p>\n

This article is about the technical and functional audit of a Dynamics CRM system<\/strong> which ensures that it will perform as expected over the time because it is properly built and maintained.<\/span><\/p>\n

<\/p>\n

General architecture and system documentation<\/span><\/span><\/h3>\n

The first task in such an auditing engagement is validating that the system is built on a solid foundation and is well dimensioned<\/strong> to support\u00a0the\u00a0requirements against it has been built.<\/span><\/p>\n

This is not only about stating that the building blocks of the system are adequate for the requirements but also they are properly sized. <\/span>Moreover, it is also about ensuring that the system is properly documented<\/strong>.<\/span><\/p>\n

It is all about answering these questions:<\/span><\/p>\n