Currently I am working on a project in California, the client has asked me to help them to put together a CRM Development Standards for the development team.  I was surprised by the request because big companies with a development team usually have the standards defined and we just need to add the Dynamics CRM portion to the standards.

Per their request, I worked with them to came up with a CRM Development Standards for our project.  I would like to share with all of you on what should be included in a CRM Development Standards document.

So, what exactly is a Development Standards?  It’s simply a document layout all of the rules to tell developers what to DO and AVOID.  I have divided the rules into three categories, which they are DO, CONSIDER and DON’T.

  • DO – This should always be followed.
  • CONSIDER – This should usually be the case, however there are known exceptions.
  • DON’T – This should never do.

In our standards document, we have the following sections:

  • Configuration Standards
    • Entity
    • Form
    • Attribute
    • Relationship
  • Customization Coding Standards
    • Naming Conventions
    • Comments
    • Client Side Coding
      • JavaScript
      • jQuery
      • HTML
      • CSS
    • Server Side Coding
      • C#
      • ASP.Net
      • MVC
  • Database Standards
    • Table
    • Store Procedure
    • Function

If you are looking for a Dynamics CRM Development Standards, the above document layout should help you to get a head start.  All you have to do now is to write your DOs and DON’Ts for your project.  I hope this helps!