When Agile meets Microsoft Dynamics CRM, Part 1: The Encounter

September 17 2013

Ever since I was introduced to the concept of agility in the context of  software development , I have been drawn by its powerful principles. However, being a Microsoft Dynamics CRM consultant I have run into occasional friction when proposing Scrum - the most popular agile development method at the moment - as the approach for a CRM implementation. In a new series of articles, I will advocate using agile methods when implementing Microsoft Dynamics CRM and aim to provide guidelines for success.

About Guus van

Guus van Waardenburg is a CRM Consultant at Avanade Netherlands. He obtained his masters degree in Information Sciences at VU University in Amsterdam. Guus is a published author, mainly on Agile adoption within Enterprise environments. With years of experience in the field of Dynamics CRM implementations - mainly in the Consumer Packaged Goods industry, and his continuous drive to explore and learn he is continuously expanding his knowledge on topics like Agile, Social Media, Gamification and other aspects in the context of Microsoft Dynamics CRM.


More about Guus van

Comments

hongfu.wang's picture

where is part2?

jgumpert's picture

The next part of this article will be up soon. We'll post a link from here too.

jmedina's picture

Jhon Dario Medina. Did you publish part 2?

JulianColeman's picture

I look forward to Part 2.

GVerreault's picture

Great post. I've been involved in large implementations of CRM, mostly in the public sector, and I gotta say that each time that we approached projects with the concepts that you describe, we've nothing but success, effective solution for the end users, delivered on budget and on time, and even sometimes before the initial due date! We actually pushed these concepts to the limit, working a lot with iterative development using CRM at the very beginning of the project. And I think that it's where Dynamics CRM excels, because of the ease of use of the various personalization tools. We're conducting design workshops with end users, and some of the requirements gathered at the beginning of the session can often be shown before the end. While we were often put in the rigid structure of public sector, and always on fixed contracts, we managed to adapt their strong methodology so it could fit the Agile approach. It's all in the work methods! I'll be waiting for the second part of your post!