New interns at Universal Containers have been tasked with following a new process to import leads from a spreadsheet into Salesforce. A business analyst is mapping the process to document the overall lead creation process.What should the process map look like?
Answer(s): A
This answer states that using a somewhat detailed process map that is easy to remember and self- explanatory is what the process map should look like for documenting the process of importing leads from a spreadsheet into Salesforce for new interns at Universal Containers. A somewhat detailed process map means that the BA includes enough information to describe the main steps, inputs, outputs, and decisions of the process, but not too much information that might overwhelm or confuse the new interns. A somewhat detailed process map can help the BA to make the process easy to remember and self-explanatory by using simple language, clear symbols, and logical flow. A somewhat detailed process map can also help the BA to provide an effective training tool for the new interns.
Universal Containers is developing a new case management solution in Salesforce. The business analyst has started writing user stories to capture feature needs. One user story is: The customer care representative wants to take ownership of new cases and communicate with customers so they can provide high-touch customer experiences."Which component of the user story is "provide high-touch customer experiences?"
Answer(s): B
The component "provide high-touch customer experiences" is the why part of the user story because it describes the benefit or value that the customer care representative will get from taking ownership of new cases and communicating with customers. The who part of the user story is "the customer care representative" because it describes the user role or persona who will benefit from the feature or functionality. The what part of the user story is "to take ownership of new cases and communicate with customers" because it describes the feature or functionality that the customer care representative wants or needs. The where part of the user story is not included in this example because it is usually captured in other documents or artifacts, such as acceptance criteria or wireframes. The assumption part of the user story is not included in this example because it is usually captured in other documents or artifacts, such as risk register or issue log.
1 https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business- analyst-certification-prep/user-stories
A business analyst captures the following acceptance criteria for a user story about case reassignment in Service Cloud.· A service manager can dick a Reassign button that changes the owner field of the case. · A service manager is able to reassign cases-as part of the mobile experience. · Reassignment functionality can be used on cases that have been auto-reassigned.· Service reps are unable to reassign cases.Which mistake was made?
The mistake made in capturing these acceptance criteria was that they include solution information instead of focusing on what needs to be achieved by implementing this feature or functionality. For example, specifying that "a service manager can click a Reassign button" implies a particular design choice rather than describing what outcome should be achieved by reassigning cases (such as transferring ownership or notifying new owners). Acceptance criteria should be aligned with the user's goal rather than prescribing how to achieve it so that they do not limit creativity or innovation in finding solutions. Acceptance criteria should also be small and testable so that they can be easily verified by using techniques such as scenarios or test cases.
The business analyst at Universal Containers is writing users stories to support the Salesforce implementation for the sales operations division.There is a request for visibility into sales rep' pipeline so that can see their revenue. Which missing component is necessary to finish this user story?
The missing component necessary to finish this user story is why because it describes the benefit or value that sales reps will get from having visibility into their pipeline revenue (such as forecasting sales performance or identifying opportunities). The who part of this user story is "sales reps" because it describes the user role or persona who will benefit from this feature or functionality. The what part of this user story is "visibility into sales rep' pipeline" because it describes the feature or functionality that sales reps want or need.
Cloud Kicks has assembled a new product team to launch a brand ambassador partner portal in Experience Cloud. The team is debating various ways to document the requirements. The business analyst recommends writing user stories within the Agile methodology. What is the benefit of creating user stories when documenting project requirements?
Answer(s): C
User stories are short descriptions of a feature or functionality from the perspective of an end user. They follow 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. User stories help translate requirements in a way that shows a product's value to the end user and helps prioritize and validate them. User stories do not provide specific details about a product early in the development lifecycle because they are usually high-level and flexible. User stories do not decrease the need for collaboration within a product team throughout the project because they require constant communication and feedback among stakeholders, developers, and testers.
1 https://parquet.dev/a-guide-to-salesforce-user-acceptance-testing/
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.