CRM Build & Release Best Practice

The below best practices should be followed while preparing build and release for Dynamics CRM application.

Please follow the below steps for Build Best Practice:

1. Automatic Build preparation is recommended for CRM. here is a detailed step by step article in this regard.
2. Use Solution Packager tool to Compress and Extract a solution zip file.  Check out here to learn how to use this tool.
3. provide a proper version of the CRM Solution build.
4. Build should be extracted from TFS with all change sets. Read a nice article here.

Please follow the below steps for Release Best Practice:

1. Incorporate the Solution Packager in your development effort and managing your CRM metadata in Source Control ensures traceability, but presents unique challenges. We will discuss how to solve these challenges and minimize the impact on developer productivity. refer this article for a better idea.
2. Structure your build effort to consume the outputs of Development and create CRM solutions from source code and Microsoft Dynamics CRM metadata.
3. Prepare for Product Up-gradation.
   • Check if any release up-gradation required URs of the product
4. Define a Release Cycle and Release Calendar
   • Prepare a release calendar with pre-planning actions and resources.
   • Limit the release cycle monthly or quarterly.
   • Inform required stack holders before every release.
5. Discuss with developers for correct release.
   • Every release contains components which needs to be deployed in up-stream environments so its always best practice to discuss with concerned developer to ensure a successful release.
6. Code Merging in TFS.
   • It is very difficult task to merge the change sets if there is multiple teams working on customizations. SO proper code merging should be followed.
7. Version Control
   • Release versions should be properly maintained. If there is any hotfix then version it properly.
8. Duties of Release Manager
   • Release manager should co-ordinate with required stack holder.
   • Inform Business for the downtime for the release.
   • Hand-over the environment to business after successful release.
9. Risk Analysis
   • Analysing the expected risk of release.
10. Manage Centralized Folder
    • All documents should be stored in a common centralized folder.

Please comment if I missed anything.