First of all, I am really sorry for this huge gap between the last post and this one, few unexpected things occurred and even though the draft was sitting on my desktop for a long time, I could not finish it sooner. I have taken a little more space and consequently few more seconds of your precious time in an effort to provide a complete view of skills (in my opinion) required at Microsoft Dynamics CRM Tech Lead level.
In this third article of the series Desired Skill Set for Microsoft Dynamics CRM Technical Resources, I will describe what is expected of a Microsoft Dynamics CRM Tech Lead.
I would like to point out an obvious fact here. If you have followed these articles from the very beginning, the skill levels are additive i.e. as we climb the hierarchy, each level includes the skillset from the previous level and additional skills.
Ideal total years of experience – 7 to 10 years
Desired technical skills
- HTML (Level 300)
- ASP.Net (Level 300)
- C# (Level 300)
- Reporting and Business Intelligence Tools (Level 300)
Microsoft PowerApps and Flow (Level 200)
- Microsoft Azure (Level 300) – Expert level command on Microsoft Azure and its integration areas with Dynamics CRM are compulsory at this stage. Additionally, understanding (Level 100-200 is sufficient where it is mentioned otherwise) of the following sub areas of Azure is an added advantage.
- Azure App Service – Level 300
- Azure Active Directory – Level 300
- Application Insights – Level 300
- API Management
- Azure Search
- Azure SQL Databases
- Redis Cache
- Data Factory
- AI + Cognitive Services
Internet of Things – Helpful with Connected Field Services
An architectural pattern is a general, reusable solution to a commonly occurring problem in software architecture within a given context. Architectural patterns are similar to software design pattern but have a broader scope. The architectural patterns address various issues in software engineering, such as computer hardware performance limitations, high availability and minimization of a business risk. Some architectural patterns have been implemented within software frameworks.
I strongly recommend a bit old book as a reference for aspiring / practicing Tech Leads / Architects: Patterns of Enterprise Application Architecture by Martin Fowler (https://www.martinfowler.com/books/eaa.html).
After you have delved in various Dynamics CRM implementations you would know that the moment you are trying to implement CRM / xRM for an enterprise, you will have to envision a bigger picture, and you certainly will not be limited to challenges presented by Dynamics CRM, in such cases, Enterprise Architecture patterns can increase your success rate by manyfold.
You may want to have a look at the previous articles of this series at: