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

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.

How Are Agile Projects Different?

Looking at software development in general, there are three project truths that present challenges: (1) It is impossible to gather all requirements at the beginning of a project, (2) whatever requirements gathered are guaranteed to change, and (3) there will always be more to do than time and money will allow. Agile accepts these truths.

First of all, agile focuses on people and their interactions rather than processes and tools. The emphasis on people is concerned with: amicability, talent, skill, and communication. This attention to the human issues gives agile projects a particular feel. Functioning effectively in an agile team requires a certain mind-set. Typically it is very difficult for agile people to function well in a rigid organization and vice versa.  Therefore agile is not for everyone ─ something an organization should consider before adopting agile.

Second, agile focuses on working software rather than comprehensive documentation. Analysis, design, development, and testing are performed continuously and in parallel as opposed to traditional sequential methods. Members of an agile team are joined at the hip working together on a daily basis throughout the project. This introduces accountability across the team for every part of the process. This requires agile team ...