The service Center at Universal Containers is deploying a new case management solution. Management has asked the project team to prepare for end user training. The project team consists of an admin and a business analyst (BA). Which task should be assigned to the BA?
A. Conduct user training
B. Create user training materials
C. Set up users for training
Explanation: A business analyst is responsible for creating user training materials that explain how to use the new case management solution. The training materials should include screenshots, videos, diagrams, and step-by-step instructions that cover the key features and functionalities of the solution. The business analyst should also ensure that the training materials are aligned with the user stories and requirements.
Northern Trail Outfitters launched a new feature on its Experience Cloud site to allow customers to compare features of similar products ahead of the major promotional event of the year. The user acceptance testing (UAT) passed successfully; however, many customers complained of issues when accessing the site. What did the business analyst overlook before recommending that the release go live?
A. The AT should have been performed with enough time to resolve bugs in the new feature.
B. The UAT should have been performed with both peak load and average load simulation.
C. The UAT should have been performed by customers who are familiar with the products.
The business analyst (BA) at Cloud Kicks is managing a project to build a recruiting app for the management and human resources (HR) teams. The HR director wants the app to help the team navigate the hiring process more efficiently. The BA designs a Stakeholder Wheel to better understand all of the people with an interest m the project. Which level of influence should the BA place the MR Director on the stakeholder wheel?
A. The Sponsor
B. The Enterprise
C. The project
Explanation:
The level influence that business analyst should place HR Director stakeholder wheel
project stakeholder wheel tool identifies understands needs expectations interests
influence power stakeholders involved project stakeholder wheel has four levels influence
sponsor project enterprise environment sponsor highest level influence project second
highest level influence enterprise third highest level influence environment lowest level
influence HR Director should placed project level influence stakeholder wheel HR Director
makes decisions determines priorities requirements project HR Director also directly
affected outcome project.
The sponsor is not level influence that business analyst should place HR Director
stakeholder wheel sponsor highest level influence stakeholder wheel sponsor provides
funding resources support project sponsor also defines vision objectives success criteria
project HR Director not sponsor project unless also provides funding resources support
project.
The enterprise is not level influence that business analyst should place HR Director
stakeholder wheel enterprise third highest level influence stakeholder wheel enterprise
includes internal individuals teams groups affected outcome project but not actively
contribute project enterprise also includes policies procedures standards guidelines govern
project HR Director not enterprise unless also affected outcome project but not actively
contribute project.
After the completion of the most recent sprint at Cloud Kicks (CK), the business analyst
(BA) provided a demo of three user stories for the customer support solution to a senior
executive. During the demo, the BA showcased the following Salesforce functionalities:
A. Confirm each user story includes a clear who, what, and why.
B. Update the environment to use language specific to CK.
C. Explain that the term is a Salesforce industry standard.
Explanation:
User stories should follow the "Who, What, Why" format to ensure clarity and relevance:
Avoiding Ambiguity: The feedback about the unclear definition of "case" highlights
a lack of context in the user story. Following the "Who, What, Why" format ensures
that stories are understandable to all stakeholders.
Best Practices: Salesforce recommends well-structured user stories to
communicate functionality clearly during demos and workshops.
Stakeholder Alignment: Including the "why" links functionality to business value,
helping stakeholders understand the purpose of features showcased.
A business analyst (BA) at Northern Trail Outfitters is mapping a workflow process to onboard a new user group to a Service Cloud implementation. Which level of detail should the BA use for the process map and why?
A. Very detailed—It should be prescriptive for new users following an unfamiliar process.
B. Somewhat detailed—Since the process will be repetitive, new users will learn and remember the details.
C. Simple—A high-level overview of the process is sufficient to show a new user experience.
Explanation: The level of detail that the business analyst should use for the process map and why is somewhat detailed. This is because the process map should provide enough information to guide new users through the onboarding process, but not overwhelm them with too much detail that may be irrelevant or unnecessary. Since the process will be repetitive, new users will learn and remember the details over time, and they can always refer back to the process map if needed. The process map should include the main steps, decisions, inputs, outputs, and roles involved in the onboarding process, as well as any exceptions or variations. The process map should also use clear and consistent terminology, symbols, and notation to ensure readability and understanding.
Page 16 out of 62 Pages |
Previous |