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

The best practice for handling an urgent, high-priority change request in Scrum is to add it to the prioritized backlog for the next sprint. This way, the change request can be reviewed by the product owner and estimated by the development team before being added to a sprint. Adding a change request to an ongoing sprint would disrupt the planned scope and schedule of work.

https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-certification-prep/manage-change-requests

https://www.scrum.org/resources/blog/how-handle-change-request-scrum

A capability model is a high-level representation of what a business does or needs to do in order to achieve its goals and objectives. A capability model can help a business analyst review the key process areas that were used for NA team with APAC team so they can scope their priorities for overall business improvement. A capability model can also help identify gaps or overlaps between different regions or teams.

https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-certification-prep/create-a-capability-model

https://www.bain.com/insights/management-tools-capability-sourcing/

This answer states that a full sandbox is what users should log in to complete their assigned testing for preparing for UAT related to an upcoming major release at Cloud Kicks. A full sandbox is a type of sandbox that copies all data and metadata from an organization's production environment into an isolated environment for development, testing, or training purposes. A full sandbox is what users should log in to complete their assigned testing because it provides a realistic and accurate representation of how the new functionality would work in production, and it allows users to test without affecting live data or operations.

Reference: https://trailhead.salesforce.com/en/content/learn/modules/application-lifecycle-and-development-models/application-lifecycle-and-development-models-sandboxes

This answer states that creating a value stream map is what the BA should do to engage stakeholders for improving the new customer onboarding experience at Cloud Kicks which involves complex handoffs between teams. A value stream map is a type of process map that shows how value flows from a customer request to a product or service delivery across different teams or departments. Creating a value stream map means that the BA works with stakeholders from different teams or departments to identify and visualize their inputs, outputs, activities, roles, etc. related to customer onboarding. Creating a value stream map is what the BA should do to engage stakeholders for improving customer onboarding because it helps them to collaborate and communicate their perspectives and expectations, and to discover and eliminate waste or inefficiencies in customer onboarding.

Reference: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-process-mapping-to-understand-your-business

This answer states that definition of done is where the BA should capture these requirements after writing user stories for developing a solution for managing leads in Sales Cloud at UC: be assigned a level of effort, be demonstrated to the stakeholder, and have documented deployment steps. Definition of done is a set of criteria that defines when a user story or a task is completed and ready for deployment or delivery. Capturing these requirements in the definition of done means that the BA specifies that a user story or a task must meet or pass these criteria in order to be considered done. Capturing these requirements in the definition of done is where the BA should do it after writing user stories because it helps the BA to clarify and communicate the expectations and standards of the user stories or tasks, and to ensure that they are met or passed.

Reference: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-user-stories-to-capture-requirements

This answer states that multiple project team members can make and view revisions is a benefit of tracking user stories in a repository for improving the case process in Salesforce at UC. A repository is a common or central location where documents or files can be stored, accessed, and updated by multiple users or teams. Tracking user stories in a repository means that the BA stores user stories in a repository, such as Jira, Trello, Asana, etc. Multiple project team members can make and view revisions is a benefit of tracking user stories in a repository because it enables collaboration and communication among project team members, and it ensures consistency and accuracy of user stories.

Reference: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-stakeholder-engagement-skills

This answer states that bringing the requirement to the product owner's attention is what the BA should do after discovering that several users indicate they use multi-factor authentication (MFA) on their phones to log in to existing systems while other users indicate they access existing systems with only username and password for conducting user interviews with the support team as part of a migration to Salesforce at Cloud Kicks. A product owner is a person who represents the voice of the customer or the stakeholder, and who is responsible for defining and prioritizing the requirements for a product or a project. Bringing the requirement to the product owner's attention means that the BA informs and discusses with the product owner about the different preferences or expectations of users regarding MFA for logging in to Salesforce. Bringing the requirement to the product owner's attention is what the BA should do after discovering this difference among users because it helps the BA to align and validate the requirement with the product owner, and to determine and propose a solution or an alternative for MFA for logging in to Salesforce.

Reference: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-stakeholder-engagement-skills

This answer states that documenting user requirements from each department during discovery sessions is what the BA should do to get buy-in from users for preparing for a new Sales Cloud implementation for 6,000 users at CK. User requirements are the needs, expectations, and objectives of the users for the Sales Cloud implementation. Discovery sessions are meetings or workshops where the BA gathers and clarifies user requirements from different stakeholders. Documenting user requirements from each department during discovery sessions means that the BA records and organizes the information obtained from different stakeholders from different departments, such as manufacturing and delivery, in a clear and concise way. Documenting user requirements from each department during discovery sessions is what the BA should do to get buy-in from users for preparing for a new Sales Cloud implementation because it helps the BA to understand and validate the user requirements, and to communicate and align them with the project scope and goals.

Reference: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-stakeholder-engagement-skills

This answer states that reviewing these user stories in the backlog at the next sprint retrospective is what the BA should do next after discovering that a few user stories are no longer needed for revamping the order management process at NTO. User stories are short descriptions of a feature or a functionality from a user's perspective. Backlog is a list of user stories that need to be prioritized and completed for a project or a product. Sprint retrospective is a meeting or a workshop where the project team reviews and reflects on their performance and progress in the previous sprint. Reviewing these user stories in the backlog at the next sprint retrospective means that the BA discusses and evaluates these user stories with the project team to determine if they are still relevant, valuable, or feasible for revamping the order management process. Reviewing these user stories in the backlog at the next sprint retrospective is what the BA should do next after discovering that a few user stories are no longer needed because it helps the BA to update and maintain the backlog, and to ensure that the user stories align with the project scope and goals.

Reference: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-user-stories-to-capture-requirements