Implementation approach insights for Microsoft Dynamics 365 Finance and Operations
• CRP: Conference room pilot CRP methodology is a blend of agile and waterfall and can smartly use this to achieve goals of all sizes, big or small. This is widely used and accepted for various cloud-based initiatives. Conference Room Pilot (CRP) is very similar to a prototyping model.
features of a CRP methodology: CRP methodology levers pilots, wherein each pilot is designed to target a specific stage, event, or business process of the enterprise during an implementation and should determine the success or failure.
It's a recurring approach and is well utilized when a larger goal is divided into many manageable goals.
It's a progressive approach which brings in smaller time to value in implementations and ensures early acceptance of a solution.
benefits of using CRP in implementations:
- Confirms and validates your understanding of business scenarios and requirements
- Less change management
- Higher adoption rate of incremental solution
- Quicker go-lives
- Validated proposed solution with early feedback
- Iterative effort
• Agile: This methodology is good in select scenarios such as development, support, enhancements, etc. However, for a greenfield initiative of implementing Microsoft Dynamics 365 for Finance and Operations, this may not always be so useful. When the project duration is short and goals are clearly defined and non-changeable, this methodology will be found useful.
• Waterfall: This is a traditional methodology, which banks on clearly defined stages and deliverables, and often is used when the duration of the project is longer. This methodology carries some risk and in contract to agile and CRP the output is not seen early enough. Usually big bang project initiatives in implementing ERP have seen using this one. In the modern cloud world, getting early stakeholder buy in is key to high adoption of new ERP and also benefits in managing change within an organization.
*This post is locked for comments