The business analyst (BA) on the Salesforce development team at Northern Trail Outfitters is leading a requirements elicitation workshop about the process for onboarding new wholesale partners. While whiteboarding the process, one stakeholder continuously interrupts and points out inefficiencies with invoicing and delivery processes.What should the BA do to prevent the session from being derailed?
Answer(s): C
The best practice for preventing a session from being derailed by an off-topic stakeholder is to use a "parking lot" technique. A parking lot is a list of topics or issues that are not relevant to the current session but may need further discussion or resolution later. The BA should add the stakeholder's concerns to a parking lot for further discussion, and acknowledge that they are important but out of scope for the current session. This way, the BA can keep the session focused on the onboarding process and avoid wasting time or losing engagement from other stakeholders.
https://trailhead.salesforce.com/en/content/learn/modules/business-analysis-process- mapping/plan-and-facilitate-a-process-mapping-session
Universal Containers (UC) needs a Quip template to create Account plans. UC's business analyst has been tasked with documenting requirements for this initiative. During one of the business requirements gathering sessions, a sales manager notes that it's important the new template is user- friendly and only accessible to the account team.Which option captures this requirement?
Answer(s): A
The option that captures this requirement is "Make the template user-friendly and accessible only by members of the account team." This option clearly states what needs to be done (make the template user-friendly and accessible) and who it is for (members of the account team). The other options are either incomplete or irrelevant. Option B does not specify what needs to be done or who it is for.Option C does not specify what needs to be done or why it is important.
https://trailhead.salesforce.com/en/content/learn/modules/business-analysis- requirements/understand-requirements
Universal Containers has asked a business analyst (BA) to assist the sales management team with a request for a new picklist field called "Lost Reason" on the Opportunity object with the goal of improving pipeline reports. After mapping the managers to the sales leader persona and obtaining feedback from them, the BA has discovered that the managers want to better understand Closed/Lost Opportunities so they can help sales teams close more deals. Which option should the BA use to construct the user story?
This answer provides an example of how to construct the user story for creating a new picklist field called "Lost Reason" on the Opportunity object with the goal of improving pipeline reports, using this format: As a <persona>, I want <goal>, so that <value>. This answer defines the persona as "sales leader", who is likely to be one of the main users or beneficiaries of this feature. It also defines the goal as "see more details on Closed/Lost Opportunities", which is what they want to accomplish with this feature. Finally, it defines the value as "help the sales team improve close rates", which is why they want to accomplish this goal and how they will measure success.
https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick- look/use-user-stories-to-capture-requirements
At Universal Containers, a business analyst (BA)r solution architect, lead developer, quality assurance lead, and other team members need access to user stories as part of the Agile lifecycle of enhancements to a Marketing Cloud integration project. What should the BA do to give all team members access and visibility to the most recent user stories as the project is in motion?
The best practice for giving all team members access and visibility to the most recent user stories as the project is in motion is to define a common repository to hold all user stories and track changes over time. A common repository is a centralized location where all user stories are stored and managed. It allows all team members to access, view, edit, comment, prioritize, assign, and update user stories as needed. It also tracks changes over time and provides version control and history of user stories. A common repository can be a tool such as Jira, Trello, Asana, or Salesforce Agile Accelerator.
https://trailhead.salesforce.com/en/content/learn/modules/business- analysis-user-stories/manage-user-stories
The sales team recently received training on a new sales methodology. When viewing an Opportunity in Sales Cloud, the sales manager wants the sales cycle to include new stages in addition to multiple custom fields. The business analyst is starting to construct user stories to support the new process.What should each user story include?
Answer(s): B
This answer states that using who, what, and why is what each user story should include for optimizing a very manual process in its Salesforce org. Who refers to the persona, which is a fictional representation of a typical user or stakeholder who will use or benefit from a feature or a functionality. What refers to the goal, which is what the user or stakeholder wants to accomplish with the feature or functionality. Why refers to the value, which is why the user or stakeholder wants to accomplish the goal, and how they will measure success. Using who, what, and why can help the BA to write effective user stories that capture and prioritize the requirements, and align them with the stakeholder value and expectations.
Post your Comments and Discuss Salesforce Certified Business Analyst exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the Certified Business Analyst content, but please register or login to continue.