Salesforce Certified Business Analyst Practice Test - Questions Answers, Page 16

The type of analysis that the BA should recommend to ensure the implementation team avoids this challenge on the current project is stakeholder analysis. Stakeholder analysis is a technique that helps to identify and understand the people who are affected by or involved in a project, and their needs, expectations, interests, influence, and attitudes towards the project. Stakeholder analysis helps to avoid missing or overlooking important stakeholders, and to plan appropriate communication and engagement strategies for each stakeholder group. The other options are either irrelevant or insufficient. Option A does not address the challenge of identifying and understanding stakeholders, but rather their behaviors and preferences. Option B does not address the challenge of identifying and understanding stakeholders, but rather their organizational context and environment.

Reference: https://trailhead.salesforce.com/en/content/learn/modules/business-analysis-stakeholder-management/identify-stakeholders

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.

Reference: https://trailhead.salesforce.com/en/content/learn/modules/business-analysis-process-mapping/create-a-process-map

This answer states that scheduling a storyboarding session is what the BA should do to help stakeholders visualize how Marketing Cloud uses insights to create journeys, when timelines are too tight to present a demo, and approval from stakeholders is needed soon in order to keep the project on track. A storyboarding session is a technique that involves creating and presenting a series of sketches or images that illustrate how a user interacts with a system or a feature. A storyboarding session can help the BA to show stakeholders how Marketing Cloud uses insights to create journeys by depicting the steps, actions, and outcomes of the process in a visual and engaging way. A storyboarding session can also help the BA to elicit feedback, validate requirements, and obtain approval from stakeholders in a timely manner.

A SIPOC diagram is a high-level process map that shows the key elements of a process, such as the suppliers, inputs, outputs, and customers. It can help identify the scope and boundaries of a process and the stakeholders involved. A capability model is a strategic tool that shows the high-level capabilities of an organization, but it does not show the details of a process.A value stream map is a detailed process map that shows the value-added and non-value-added activities, cycle times, wait times, and other metrics of a process, but it may be too complex for capturing key points.

Reference:1https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-certification-prep/collaborate-with-stakeholders

The business analyst should prioritize US-4007 and US-4009 because they are the most critical work items. US-4007 is the work item that will allow customers to submit support tickets, and US-4009 is the work item that will allow customer service representatives to view and respond to support tickets. These two work items are essential for the MVP to be functional.

US-4008 is a less critical work item because it will allow customers to track the status of their support tickets. This work item is important, but it is not essential for the MVP to be functional.

US-4010 is the least critical work item because it will allow customers to rate the quality of customer service. This work item is important, but it is not essential for the MVP to be functional.

In conclusion, the business analyst should prioritize US-4007 and US-4009 because they are the most critical work items. These two work items are essential for the MVP to be functional.

A functional requirements specification is a document that describes the software and behavioral requirements of an application, such as what features it should have and how it should behave under different scenarios. It can help communicate the expectations and needs of the stakeholders to the development team. A scope statement specification is a document that defines the project scope, objectives, deliverables, assumptions, constraints, and exclusions. It does not describe the software and behavioral requirements of an application. A system requirements specification is a document that describes the technical requirements of an application, such as hardware, software, security, performance, and reliability.It does not describe the software and behavioral requirements of an application.

Reference:1https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-certification-prep/requirements

A user story is a short description of a feature or functionality from the perspective of an end user. It follows the format ''As a <who>, I want <what>, so that <why>''. The who is the user role or persona who will benefit from the feature or functionality. The what is the feature or functionality that the user wants or needs. The why is the benefit or value that the user will get from the feature or functionality.The when and where are not part of a user story format because they are usually captured in other documents or artifacts, such as acceptance criteria or wireframes.

Reference:1https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-certification-prep/user-stories

The likely cause of the issue was that the project team failed to discuss the user stories as a group before writing them. This could lead to misunderstandings, misalignment, or missing information among the stakeholders and the business analyst. The best practice for writing user stories is to collaborate with all relevant stakeholders and use techniques such as brainstorming, story mapping, or story splitting to elicit and prioritize user needs. The user stories should also be validated and reviewed by all stakeholders before finalizing them. The user stories focusing on well-defined personas is not a likely cause of the issue because personas are useful tools to represent different types of users and their goals, needs, and pain points.The acceptance criteria of the user stories being too specific is not a likely cause of the issue because acceptance criteria are statements that define how to verify that a user story is completed and meets the user's expectations.

Reference:1https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-certification-prep/user-stories