- Email support@dumps4free.com
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
| Page 1 out of 62 Pages |