Universal Containers is focused on an initiative to streamline its channel management processes. Due to the level of complexity, the business analyst (BA) will gather and document the key points in preparation to build a more detailed process map.Which diagram should the BA use in this case?
Answer(s): A
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.
1 https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business- analyst-certification-prep/collaborate-with-stakeholders
Universal Containers is implementing a Salesforce solution that's designed to transform its customer service division. During sprint planning, it was determined that the development team would be able to successfully deliver all remaining work items. However, due to unplanned delays, the development team is now at risk of being unable to complete the work items.The project manager has asked for the business analyst's (BA) help to prioritize the remaining work items. The development team has 16 hours of capacity remaining and is focused on launching a minimum viable product (MVP) of the customer service solution as soon as possible. Which work items should the BA prioritize with the remaining 16 hours of development capacity?
Answer(s): B
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.
Northern Trail Outfitters follows an Agile methodology for its Marketing Cloud projects. The project team creates several types of documents.Which document should a business analyst use to. capture the software and behavioral requirements of the application?
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.
1 https://trailhead.salesforce.com/en/content/learn/modules/salesforce- business-analyst-certification-prep/requirements
The business analyst at Cloud Kicks is beginning to write user stories for its Salesforce implementation.Which three components should-be included when writing a user story?
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.
1 https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business- analyst-certification-prep/user-stories
Cloud Kicks is planning to create a new Service Cloud console app for its services team to resolve issues with delayed shipments to customers. The business analyst (BA) wrote the user stories based on a written list of requirements provided by the manager of the services team. Upon stakeholder review with the entire services team, many of the user stories were rejected and the BA had to revise them.When the BA wrote the initial user stories, what was the likely cause of the issue?
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.
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.