Download Full Version Certified-Business-Analyst Salesforce Exam

The best practice for identifying which stage in the sales process the industry standard due-diligence should be embedded is to develop a process map as a base, work with stakeholders to understand the trigger point, and locate the stage. This practice helps to:

• Develop a process map as a base: This provides a visual representation of the sales process, showing the steps, inputs, outputs, roles, and decisions involved in each stage.
• Work with stakeholders to understand the trigger point: This helps to elicit feedback and insights from the stakeholders who are familiar with or affected by the sales process, and identify when or why the industry standard due-diligence is needed or required.
• Locate the stage: This helps to determine where in the sales process the industry standard due-diligence should be embedded, based on the trigger point and the business logic. References: https://trailhead.salesforce.com/en/content/learn/modules/business-analysis-process-mapping/create-a-process-map

This answer states that documenting user requirements from each department during discovery sessions is what the BA should do to get buy-in from users for preparing for a new Sales Cloud implementation for 6,000 users at CK. User requirements are the needs, expectations, and objectives of the users for the Sales Cloud implementation. Discovery sessions are meetings or workshops where the BA gathers and clarifies user requirements from different stakeholders. Documenting user requirements from each department during discovery sessions means that the BA records and organizes the information obtained from different stakeholders from different departments, such as manufacturing and delivery, in a clear and concise way. Documenting user requirements from each department during discovery sessions is what the BA should do to get buy-in from users for preparing for a new Sales Cloud implementation because it helps the BA to understand and validate the user requirements, and to communicate and align them with the project scope and goals. References: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-stakeholder-engagement-skills

The final step that a business analyst should perform during the user acceptance testing process that would ensure a “go” decision is to get written sign-off from all business stakeholders. Written sign-off means obtaining formal approval or confirmation from the business stakeholders that the system or solution meets their requirements or expectations and is ready to be released to production. Written sign-off helps to ensure a “go” decision by demonstrating that the system or solution has passed all the tests or validations, as well as resolving any issues or risks that may prevent the release. Written sign-off also helps to document and communicate the completion and acceptance of the user acceptance testing process. References: https://trailhead.salesforce.com/content/learn/modules/user-acceptance-testing-video/learn-about-user-acceptance-testing

A use case is a type of documentation that describes how a user interacts with a system to achieve a specific goal. It is written from the user’s point of view and follows a standard format of “A [user role] wants to [goal] by [steps]”. A use case helps to capture the user’s needs and expectations from the system and provides a basis for developing test cases and acceptance criteria. A BA should use use cases to document how users will interact with the system and what outcomes they expect from it. References: https://trailhead.salesforce.com/en/content/learn/modules/business-analysis-functional-requirements/write-use-cases

This answer points out that the previous VP’s requirements may differ from those of the new executive as the largest risk with this approach of using the inherited requirements in lieu of a traditional discovery process for a Sales Cloud implementation. Requirements are statements that describe what a solution must do or have to meet the needs and expectations of the stakeholders or users. Requirements may change over time due to various factors, such as business goals, market trends, customer feedback, or stakeholder preferences. Using the previous VP’s requirements without validating them with the new executive may result in a solution that does not align with their vision, strategy, or value proposition. References: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-user-stories-to-capture-requirements