1. Know Your Audience
For many clients, this will be their first foray into the Oracle ecosystem. Strive to understand their business needs as well as their process and nomenclature; this allows you to translate the overwhelming Oracle acronym data dictionary into terms they can relate to their own.
Make sure you know what is in scope for the project. There should never be any question as to what functionality that you are responsible for implementing. If it is not clearly spelled out in the SOW it should not be configured or tested.
You should have a plan going into any session; time can be on your side if you use it wisely. A detailed agenda should be developed and distributed prior to the CRP which clearly outlines the high level agenda, expected time for each session, and a list of required participants. Scenarios should be developed and reviewed with the customer. Data to be used in those scenarios should be clearly defined and approved by the business stakeholders. Finally, a meeting that provides a clear concise explanation of what a CRP is, what the expectations of the event are, and expected outcome should be held with the client prior to the event to ensure proper expectations on all sides.
Never take for granted that just because you set something up and did preliminary testing that it will work. Ensure you test with the scenarios and data you agreed upon with the customer. You do not want to get into a session to first find out a set up was missed or you don’t have all the information you need to conduct the CRP. Perception is everything.
Jaret Balter is the Director, Applications Delivery at Apps Associates LLC. With 13 years of SCM consulting experience across a wide of range of industries, Jaret brings a track record of implementing successful projects, helping develop more refined business processes and training clients to leverage the most out of their ERP system and solutions.