In Deciding How to Implement That Microsoft Dynamics CRM Project, Allow for the Application’s Special Complexity
To make the right choice for resourcing your project, you need to allow for these three considerations:
1. Knowledge. Microsoft Dynamics CRM requires a wide variety of skills. The application has impact on active directory, MS SQL Server, MS Exchange (optional), workstation, network environment, etc. In most cases, the IT department is divided in classic/traditional structure, which could lead to the following issues:
- The need for cross-department knowledge;
- The tendency of employees to be interested or specialized in only one field;
- Lack of experience wth the product or knowledge about best practices in development
2. Commitment. In many organizations, there is a "boundary" between ICT, Business and other departments. The commitment is to either the technical side or the business side. This could lead to:
- People losing interest in a project due to interest in only one technique and try to get into another project;
- Due to lack of cooperation between departments, the project will fail and CRM wouldn''t be used by any department;
- The maintenance and support becomes an issue, because of lack of commitment and interest in the product;
-
The introduction involves adaption
of a new system and usually a more structural way of working, which could end in
not using the system, like an old habit people tend to fall back on as ...
FREE Membership Required to View Full Content:
Joining MSDynamicsWorld.com gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more. You can also receive periodic email newsletters with the latest relevant articles and content updates.
Learn more about us hereor login