Deployment methodologies, Part 2: Is agile, waterfall, or another best for Microsoft Dynamics projects?

July 26 2017

Following is the second in a four-part exploration of deployment methodologies used by Microsoft Dynamics partners. Part 1 explores the promise of proprietary methodologies. Part 3 focuses on defining project success.

About Alan R. Earls

Alan R. Earls is a technology writer based near Boston. He has covered all facets of IT, including ERP and CRM for many years and wrote regularly on Dynamics for Microsoft's 'Momentum' midsize business website. He is the author of several books on tech and business history, including Digital Equipment Corporation and Route 128 and the Birth of the Age of High Tech.

More about Alan R. Earls

Comments

Peter Lomman's picture

I always enjoy reading alternative perspectives for application deployment, but having been in the front line of quite a few system implementations I have discovered that it is more about involvement and engagement with the people that will manage the outcomes and use the system. Sometimes this requires some considerable education to enable these key resources to understand the importance of process integration across the functional areas of the business. This elevates the focus to the best outcome for the business rather than the simplistic efficiency gains in a series of functional departments. Any methodology is just another perspective, and set of tools and guidelines available for the Deployment Leader. Recognizing what fits the objectives and culture, and what will deliver the best outcomes remains the responsibility of the Project Leader. Being aware of alternatives and blending them to suit individual projects is what makes deployment management more art than science. I cant wait for the next installment to see how others blend the available methodologies. Peter NAV Project Manager

jgumpert's picture

Thanks for sharing, Peter. No doubt, the abilities you describe are not easy to find.