SalesForce CERTIFIED-BUSINESS-ANALYST - Questions & Answers

The business analyst should seek sign-offs from the business for the functional requirements, individual test case functionality, and final go live date. The functional requirements are the statements that describe what the solution must do or provide to meet user needs or business objectives. The individual test case functionality is the verification that each test case meets the acceptance criteria for the corresponding user story or requirement. The final go live date is the date when the solution will be released to production and available for users or customers. These sign-offs help to ensure that the solution is complete, satisfactory, and ready for launch.

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.
References:
https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-process-mapping-to-understand-your-business

The next step that the business analyst should take is to review the user stories to ensure they are small, testable, and valuable. User stories are statements that capture a requirement or feature from an end user's perspective. They should be small enough to be completed within a sprint, testable enough to be verified by acceptance criteria, and valuable enough to deliver benefits or outcomes for end users.
Reviewing user stories can help UC understand why development and testing took more time than expected, and how to improve them for future sprints.Creating a SWOT (Strengths, Weaknesses, Opportunities, Threats) analysis to understand why development and testing took more time is not a good next step because it is a strategic tool that evaluates the internal and external factors affecting a project or initiative, not a tactical tool that evaluates the quality or effectiveness of user stories. Moving the deployment date out so the teams have more time to work is not a good next step because it does not address the root cause of why development and testing took more time, and it may affect the project scope or budget.
References:
https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/user-stories
https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/user-acceptance

The document that the BA should review and revise to provide more clarity to the team is acceptance criteria. Acceptance criteria are statements that define what conditions or requirements must be met for a user story or sprint to be accepted by the user or stakeholder. Acceptance criteria help to clarify the scope, functionality, and quality of the user story or sprint, provide a basis for testing and validating the work done, and ensure that it meets the user's needs and expectations. By reviewing and revising acceptance criteria for the user story about an Opportunity email alert, the BA can provide more clarity to the team about what type of testing is needed.
References:
https://trailhead.salesforce.com/en/content/learn/modules

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.

The primary value of the business analyst (BA) speaking with customer service reps during the discovery for a new Service Cloud implementation is validating current processes. Customer service reps are the end users of Service Cloud and they can provide valuable insights into how they perform their tasks, what challenges they face, and what expectations they have from the new system. The BA can use this information to validate or update the current process maps and identify areas for improvement. Estimating the project cost is not a value of speaking with customer service reps, as this is usually done by project managers or sponsors based on resource allocation and budget constraints. Building solution design consensus is not a value of speaking with customer service reps, as this is usually done by solution architects or developers based on technical feasibility and best practices.
References:
https://trailhead.salesforce.com/content/learn/modules/business-analysis-for-salesforce-projects/
understand-the-salesforce-implementation-lifecycle (https://trailhead.salesforce.com/content/learn/modules/business-analysis-for-salesforce-projects/analyze-business-processes-and-requirements)

The role of the Business Analyst aligns with CK's needs for analyzing data, understanding business processes, and guiding implementation: Core Responsibilities: A BA bridges the gap between business needs and technical solutions, ensuring optimal process improvements like the lead-to-cash process. Salesforce Role Expectations: Salesforce BAs are trained to analyze data, document processes, and recommend best practices for implementations.
Collaborative Approach: A BA works closely with stakeholders, solution architects, and administrators to
ensure successful project delivery.

The acceptance criteria that is most appropriate for this user story is sales rep can see the inventory closest to a customer with a quick action. Acceptance criteria are specific conditions or requirements that must be met for a user story to be considered done or acceptable. Acceptance criteria should be clear, concise, testable, and measurable. Sales rep can see the inventory closest to a customer with a quick action is an appropriate acceptance criterion because it specifies what functionality or feature must be delivered (see the inventory closest to a customer), how it must be delivered (with a quick action), and who must be able to use it (sales rep). As a sales rep, I see the inventory closest to a customer is not an appropriate acceptance criterion because it does not specify how the functionality or feature must be delivered or accessed by the user. It is also redundant with the user story format of "as a [role], I want
[what], so that [why]". Sales rep can see the inventory closest to a customer is not an appropriate acceptance criterion because it does not specify how the functionality or feature must be delivered or accessed by the user. It is also vague and incomplete as it does not indicate what constitutes "closest" or how it is measured.
References:
https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-certification-prep/
user-stories

The user story should focus on customer experience. Customer experience is the perception and feeling that a customer has when interacting with a product or service. Customer experience is a key factor that influences customer satisfaction, loyalty, retention, and advocacy. A user story should focus on customer experience because it helps to define the value or benefit that the customer expects from the product or service, and provides a basis for designing and developing the solution that meets or exceeds the customer's needs and expectations. The other options are either irrelevant or incomplete.
Option A does not focus on customer experience, but rather on sales margins, which are an internal metric that may not reflect the customer's perception or feeling.
Option C does not focus on customer experience, but rather on product functionality, which is only one aspect of customer experience and may not address the customer's emotional or psychological needs.
References:
https://trailhead.salesforce.com/en/content/learn/modules/business-analysis-user-stories/write-user-stories