Skip to main content

Building a Team for a Dynamics 365 (formerly CRM) Implementation



For most organizations, implementing Microsoft Dynamics 365 (formerly Dynamics CRM) is a team effort.  The size and composition of the team will depend on the scope of the implementation, the timetable, and related efforts such as data migration and integrations.

Here are the roles that my company InfoStrat typically sees for a medium-sized implementation project:

  1. Project Manager. The PM and the technical lead are the most critical roles on the project.  A large project may also include a deputy project manager to cover when the PM is not available.  Prior experience with Dynamics 365 is valuable to understand how an off-the-shelf implementation is different from a custom software development project.  Most of our projects follow an Agile development methodology, so this post assumes Agile in describing the roles of the team members.  
  2. Technical Lead.  The tech lead is the senior technical team member and provides technical direction to the team.  Prior Dynamics 365 implementation is mandatory for the tech lead, and business domain knowledge is highly desirable.  Technical leads often have titles such as "software architect."
  3. Business Analyst. The BA interviews users, analyzes requirements and creates user stories which describe how business scenarios are automated. Prior experience with the Dynamics 365 version used in the project is valuable and business domain knowledge is critical. 
  4. Developers.  You may need developers for several aspects of the implementation, such as the portal, integrations, and data transformation or migration.   These developers should be proficient with the tools needed for their aspects of the project.
  5. Testers.  Experienced testers will contribute to the quality of the solution.  They should be engaged early in the project so that they are already familiar with user stories when testing starts. 
  6. Trainers.  Training is essential to successful adoption of the solution.  In Agile, the training can start early in the process for users who are participating in sprints.  You may want to record videos of training to make them available to users who cannot attend in-person training sessions.
Some roles lend themselves to be combined where team members have the right skills for more than one role.  For instance, some business analysts are also skilled as trainers, and their knowledge of requirements will make them more successful in training than a trainer brought in at the end of a project with too little preparation time.

The developer role tends to scale up more than other roles, because development tasks may be divided and run in parallel.  The technical lead can determine the optimum size for development teams and manage dependencies among modules.

Popular posts from this blog

Power Apps Portal: The Successor to Microsoft Dynamics Portal

In case you have been reviewing Microsoft's new pricing for its Dynamics products which was released this month and have been unable to find Dynamics Portal, it has been rebranded as Power Apps Portal and shifted to the Power Apps side of the Microsoft product family. Rebranding the portal product underscores the importance of app scenarios involving external users such as customers and suppliers.  It also provides a simpler interface than Dynamics 365 for occasional users. The new portal pricing is based on the number of unique users who log into the portal each month (for authenticated users) and on the number of page views for anonymous users.  "A login provides an external authenticated user access to a single portal for up to 24 hours. Multiple logins during the 24-hour period count as 1 billable login. Internal users can be licensed either by the PowerApps per app or per users plans, or a qualifying Dynamics 365 subscription." Pricing starts at $200/mo

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do not require advan

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun