A business analyst (BA) at Northeren Trail Outfitters has been asked to explain a sales process improvement idea and collaborate on a plan for implementation. Several sale users in various locations have been identified to participate. Which technique should the BA use to optimize effectiveness and build a shared understanding of the idea and approach?
A. Demo prototype
B. Virtual whiteboard
C. One-on-one meetings
Explanation:
A virtual whiteboard is a technique that a business analyst can use to optimize effectiveness and build a shared understanding of an idea and approach with sales users in various locations. A virtual whiteboard is an online tool that allows multiple participants to collaborate visually by drawing, writing, or annotating on a shared screen. It can help them brainstorm ideas, create diagrams, or give feedback in real time. A demo prototype is a technique that can be used to show how an idea works or looks like, but not to collaborate on it. One-on-one meetings are techniques that can be used to communicate with individual stakeholders, but not with a group.
References:
https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/collaboration-with-stakeholders
https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/user-stories
After stakeholders formally signed off on requirements, the business analyst (BA) received numerous emails requesting changes to Salesforce during uses acceptance testing (UAT). The BA quickly became overwhelmed by the requests and needs a way to organize and peritonitis them.
What should the BA use to help them organize these requests?
A. Change request log
B. Scope statement specification
C. Gap analysis document
Explanation:
This answer states that change request log is what the BA should use to help them organize and prioritize requests for changes to Salesforce during UAT after receiving numerous emails from stakeholders who formally signed off on requirements. Change request log is a document or a file that records and tracks requests for changes to a project or a product, such as adding, modifying, or removing a feature or a functionality. Change request log is what the BA should use to help them organize and prioritize requests for changes to Salesforce during UAT because it helps the BA to manage and monitor the requests for changes, and to evaluate and approve or reject them based on their impact, urgency, or feasibility.
References:
https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-stakeholder-engagement-skills
The business analyst (BA) at Universal Containers has been capturing the requirements for a major Sales Cloud release. An admin has been deploying the resulting system changes. The quality assurance (QA) team has run into challenges when testing the changes. The BA is unaware of deployment and testing challenges. What should the BA do to resolve these challenges with the release team?
A. Associate each set of metadata -changes to the corresponding user story.
B. Provide detailed test cases to validate the functional requirements
C. Involve the stakeholders in the business requirements gathering sessions.
Explanation:
This answer states that associating each set of metadata changes to the corresponding user story is what the BA should do to resolve these challenges with the release team. Metadata changes are modifications to the configuration or customization of Salesforce, such as fields, objects, layouts, workflows, or apex code. Associating each set of metadata changes to the corresponding user story can help to track and manage the changes, and link them to the business requirements and acceptance criteria. This can also help to improve the communication and collaboration between the BA, the admin, and the QA team, and avoid any confusion or errors during deployment and testing.
References:
https://trailhead.salesforce.com/en/content/learn/modules/application-lifecycle-and-development-models
Business users at cloud kicks have just completed user acceptance testing for a Commence cloud implementation. The senior executives want to understand has successful testing was and have asked the business analyst to calculate the success rate. How is the success rate calculated?
A. Number of failed test cases divided by total number of test cases
B. Total number of test cases divided by number of passed test cases
C. number of passed test cases divided by total number of test cases
Explanation:
This answer states that number of passed test cases divided by total number of test cases is how the success rate is calculated after completing user acceptance testing (UAT) for a Commerce Cloud implementation at CK. Test cases are scenarios or steps that verify or validate if a feature or a functionality meets the acceptance criteria or requirements. Passed test cases are test cases that meet or pass the acceptance criteria or requirements. Total number of test cases are all test cases that are executed or performed for UAT. Number of passed test cases divided by total number of test cases is how the success rate is calculated because it measures how many test cases meet or pass the acceptance criteria or requirements out of all test cases executed or performed for UAT.
References:
https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-user-stories-to-capture-requirements
The project team at Cloud Kicks is under a tight deadline to implement a new Service Cloud feature. The business analyst, BA) has received feedback from the customer that the existing functionality is difficult to use. The BA wants to better understand the customers pair points before writing requirements. Which document should the BA use?
A. Journey map
B. Process map
C. Capability map
Explanation:
This answer states that using a journey map is what the BA should use to better understand the customers pain points before writing requirements for Cloud Kicks who will launch a new customer experience portal. A journey map is a diagram that shows how a customer interacts with an organization across different touchpoints or channels over time. A journey map can help the BA to better understand the customers pain points by identifying where, when, why, and how the customer experiences frustration, dissatisfaction, or difficulty with the current service or solution. A journey map can also help the BA to empathize with the customer and to design a better customer experience that meets their needs and expectations.
References:
https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-stakeholder-engagement-skills
A sales manager express frustration that the sales team is failing to enter calls in salesforce. The manager is hoping to resolve the issue quickly and has limited time and budget to complete revamp existing tools and process, the sales manager reaches out to the business analyst (BA) for recommendation. What should the BA do next?
A. Engage a developer to scope a custom solution
B. Research third-party apps on the AppExchange.
C. Export a weekly report of user activity.
Explanation:
This answer suggests researching third-party apps on the AppExchange as the next thing that the BA should do after a sales manager expresses frustration that the sales team is failing to enter calls in Salesforce, and hopes to resolve the issue quickly and has limited time and budget to complete revamp existing tools and process. The AppExchange is an online marketplace where customers can find, try, buy, and install apps that extend the functionality of Salesforce.
Researching third-party apps on the AppExchange can help the BA to find a possible solution that can address the issue of entering calls in Salesforce without requiring a lot of time, budget, or customization. Researching third-party apps on the AppExchange can also help the BA to compare different features, prices, ratings, and reviews of various apps that can meet the sales manager’s needs and expectations.
References:
https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-stakeholder-engagement-skills
At the start of a new Agile development project, the Universal Containers' product owner asked the business analyst (BA) to clearly define the intended results of the work based on stakeholder needs. The development and implementation teams will use the intended results to plan product decisions. The definition should avoid assumptions and focus on stakeholder value. Which element should the BA choose to define the intended results?
A. Requirements
B. User stories
C. Epics
Explanation:
This answer chooses user stories as the element that the BA should use to define the intended results of the work based on stakeholder needs. User stories are short and simple descriptions of a feature or a functionality from the perspective of an end user or a stakeholder. User stories can help the BA define what stakeholders want to accomplish, why they want to accomplish it, and how they will measure success. User stories can also help the development and implementation teams to plan product decisions based on stakeholder value.
References:
https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-user-stories-to-capture-requirements
Cloud Kicks will launch a new customer experience portal. During discussions with the VP of customer service, a business analyst (BA) recorded the following:
• All logins must use multi-factor authentication (MFA).
• Portal pages should load within 2 seconds.
How should the BA document the items?
A. functional requirement
B. Non-functional requirement
C. User story
Explanation:
The items that the business analyst documented are non-functional requirements. Non-functional requirements are statements that describe how a system or solution should perform, behave, or appear, rather than what it should do or provide. Non-functional requirements can include aspects such as usability, reliability, security, availability, scalability, etc. Non-functional requirements help to ensure that the system or solution meets the quality standards and expectations of the stakeholders or users. The items that the business analyst documented are non-functional requirements because they specify how Sales Cloud should perform (portal pages should load within 2 seconds) and behave (all logins must use multi-factor authentication).
References:
https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/requirements-management
Universal Containers is developing a new recruitment app using Service Cloud. The project team has started writing user stories including:
"As a human resources (HR) manager, I need to document the progress of a candidate's submission so I can manage the candidate's application throughout the recruiting process."
What is one definition of done for this user story?
A. The Candidate Status field can be updated.
B. The acceptance criteria has been approved.
C. The Candidate object has Edit access.
Explanation:
A definition of done is a set of criteria that determines when a user story is completed and ready for deployment. It typically includes technical, functional, and quality aspects of the user story, such as code quality, unit testing, documentation, performance, security, and usability. One possible definition of done for this user story is “The Candidate Status field can be updated.” This criterion checks if the functionality of updating the candidate’s submission progress is working as expected and meets the user’s need.
References:
https://trailhead.salesforce.com/en/content/learn/modules/business-analysis-user-stories/define-done
The business analyst at Cloud Kicks is using a checklist to assess the quality of user stones for an upcoming Experience Cloud implementation. Which characteristics make a user story successful?
A. Clean Direct, Concise, Cross Functional, Configurable
B. Actionable., Concise, Testable, Solution-oriented, Defined
C. Independent, Negotiable, Valuable, Estimable. Small, Testable
Explanation:
These are the characteristics that make a user story successful, according to the INVEST acronym. A user story should be independent of other user stories, negotiable in terms of scope and details, valuable to the user or customer, estimable in terms of effort and time, small enough to fit in a sprint or iteration, and testable with clear acceptance criteria.
References:
https://trailhead.salesforce.com/content/learn/modules/user-story-creation/learn-about-user-stories
| Page 1 out of 31 Pages |
Copyright © - All Rights Reserved