Upon collecting information from the customer in detail, it's time to analyze and come up with your understanding of what they need. Document all the open questions you want to discuss further to get ready to lead the discussions about requirements. It's a must to understand the requirements in depth, and this can be easily achieved by engaging the customer and asking the right questions.

In the leading process, we expect the solution advisor and implementation partner/consultant to be on top of the following activities:

• Seek the business process flow in detail and ask for a walk through.
• Get the business rules defined at various decision points in the flow chart.
• Validate the completeness of requirements coverage, dependencies, and business rules.
• Understand and document the pain areas and ask questions to clarify if you have any doubts.
• Never assume a requirement; always get it validated
• Avoid discussions about solutions in the requirements meetings; this will dilute the purpose of the requirements workshop.
• Avoid spending time discussing the out-of-scope areas until the client has approved the change order.
• Project derailment happens when scope creeps are allowed.
• It is in the interest of the customer and external stakeholders of the project to keep the requirements/scope in check.
• Capture the details of reporting, security, integration, and data migration along with the other requirements discussions.
• Non-functional requirements play a key role in shaping project success.
• Avoid using Dynamics terminologies or acronyms (for example, posting profile, value models, and so on, during CRP discussions).
• Usage of short forms early in the discussion activity should be avoided, as these may prolong or confuse the stakeholders' understanding, as they may be unaware of such terminologies or acronyms.
• Once the requirements have been heard and you have led the discussion, it's time to strike a balance between business and project goals and constraints.

Upon listening to and leading the business conversations, it is time to get back to your drawing board to work out all the solution capabilities available as per the project scope and accordingly initiate the next activity of negotiating, as described in the next subsection.