Our example is based on a typical customer undergoing Dynamics 365 for Finance and Operations, Enterprise edition (AX) implementations and how to leverage the CRP methodology.

Here is the business background: 

• Consider a customer who is into hi-tech manufacturing of public safety goods. The customer is keen to know more about how Dynamics 365 for Finance and Operations, Enterprise edition (AX) could support their particular division undergoing business transformation.
• We start the initiative with the CRP goal of going live with a business solution to support their transformation initiative.
• We need to plan for the number of pilots in Dynamics 365 for Finance and Operations, Enterprise edition (AX) by dividing the larger goal into smaller manageable ones.

Let's now see how a CRP approach can be used to accomplish the business goals:

1. Conduct multiple CRP sessions to understand the division operations. You may select a top-down approach or a scenario-driven approach; either way, the goal is to understand the entire business need. This helps in visualizing the big picture.
2. Validate your business scenario understanding and prepare the solution options. The solution preparation needs to give as much emphasis as possible to out-of-the-box capabilities, and where a tailor-fitting situation arises, think of enhancements/customization. Always prepare a solution blueprint, covering end-to-end business scenarios, and validate with the stakeholders that it achieves the business objectives:
   • First prepare all the solution proposals for out-of-box functionalities before even envisioning customization
   • Run CRP sessions to configure, demonstrate, and test the out-of-box functionalities so as to get the stakeholders' early involvement and buy in
   • Once all the out-of-box capabilities are tested, it is a good idea to then envision the solution for gaps
   • As a thumb rule, look for viable workarounds and seek validation with stakeholders
   • When no workaround exists, prepare the solution , present them with visual aids to the stakeholders, and perform a SWOT (strength, weakness, opportunities, threats) analysis jointly

3. After conducting solution CRP sessions and getting a confirmation from the stakeholders, it is time to scope the CRP:
   • Prepare a Requirements Traceability Matrix (RTM) and ensure that all the business scenarios, requirements, solution, and proposals are well-documented and signed off
   • Emphasis must be given on key decisions, taken collectively by stakeholders
   • Also, set a time to review the contract and make any amendments with more insights into the business and the solution
4. After the stakeholders are on board with the solution, start building a working solution for all out-of-box functionalities:
   • Reuse the visuals and SWOT analysis to build/develop a solution for the gaps
   • Follow the prototyping approach in development and ensure that the core gap is designed first
5. Act as a solution champion/advisor and lead the pilot with all the stakeholders. This one is easier said than done; one must always lead by example and ensure that all the ambiguities are funneled through a detailed brainstorming:
   • Embracing abstractness and converting it into concrete elements is the sign of a true leader
   • Bearer of all the key decisions that are made and going to be made
6. Now is the time to put all the hard work into action. Book several demonstration sessions with the stakeholders, based on the scope of the pilot:
   • Always start with the end-to-end solution blueprint and then demonstrate the business scenarios in the solution
   • It always helps to ensure that the highest impact scenarios are covered first and given priority
   • Seeing feedback is a must and should become part of the RTM as well in-line with change control and governance processes

Now that you have understood the CRP methodology with an example, we will now take a deep dive into some other models.