The combination of Microsoft Dynamics CRM and Microsoft SharePoint is powerful - Mix in Silverlight, scriptlets, good CRM, web and workflow design techniques and a dash of JAVA and pow and yet I have yet to totally see adoption and the right buzz around it. For instance I have seen Microsoft regional offices doing SharePoint and Office Demonstrations without CRM (confusing for this CRM Lady)
Is some of this because the bundle's icing often takes a developer in addition to other very different team members?
Is it because the vendor culture leans towards Microsoft Partners "getting it" and "doing it" and bring it together? Yet the requirements push the envelope when it comes to traditional Microsoft partner structure on either the Dynamics or the Information Technology consulting firm (ITC) model.
This new team culture could easily consist of a melding of:
1) Developer (.Net, JAVA, able to see outside their former development focus to adopt a mixed development platform. They need to work with built applications (XRM) and they should think like an ISV building libraries of scriptlets, living code that will take care and feeding and source potentially impacted by releases to the XRM platform)
2) CRM Industry expert (knowledge and understanding of the CRM industry and what a highly adopted CRM application can do for a business, as well as insight into failures and experience helping to move a company in high technology adoption) Sales process and Sales "think" and/or Service process and Service "Think" understanding is a very valuable addition.
3) Web Page Focus (background in the web page industry - knowledge management, search content key word placement, search engine optimization, usability, serving up )
4) Marketing (new edge graphics understanding, Depth of around what Silverlight can do, understanding of what publishing tools are available, Creates graphics and color mastery, creative)
5) Project manager to set expectations and who understands the first four backgrounds, skills, habits and how much time it takes for each to do what is requested. Sets budgets and time....
6) Business Process Engineering, Usability, Workflow development around how data flows from point A to point B and the corporate asset potential around the time management and data management of this data. Similar to the Manufacuturing process engineers of earlier days.
The new team is different than anything Microsoft has done before and very different from many of the partner cultures.