Salesforce Updated Certified-Business-Analyst Exam Questions and Answers by saffron

Some communication best practices that a BA should follow to become a trusted advisor to UC stakeholders are:

• Ask questions and document the answers: This helps to understand the stakeholders’ needs, expectations, pain points, goals, and priorities. It also shows interest and curiosity in their perspectives and opinions, and helps to clarify any assumptions or ambiguities.
• Make suggestions based on previous project success: This helps to demonstrate expertise and experience in Salesforce implementations, and provide valuable insights and recommendations for UC stakeholders. It also shows confidence and credibility in delivering solutions that meet their needs.
• Provide a meeting agenda prior to each session: This helps to set clear expectations and objectives for each meeting, and ensure that all relevant topics are covered. It also shows respect for the stakeholders’ time and availability, and helps to keep the meeting focused and productive. References: https://trailhead.salesforce.com/en/content/learn/modules/business-analysis-stakeholder-management/communicate-with-stakeholders

The business analyst should prioritize US-4007 and US-4009 because they are the most critical work items. US-4007 is the work item that will allow customers to submit support tickets, and US-4009 is the work item that will allow customer service representatives to view and respond to support tickets. These two work items are essential for the MVP to be functional.

US-4008 is a less critical work item because it will allow customers to track the status of their support tickets. This work item is important, but it is not essential for the MVP to be functional.

US-4010 is the least critical work item because it will allow customers to rate the quality of customer service. This work item is important, but it is not essential for the MVP to be functional.

In conclusion, the business analyst should prioritize US-4007 and US-4009 because they are the most critical work items. These two work items are essential for the MVP to be functional.

A user story is a type of documentation that describes what functionality a system should provide from a user’s perspective. It is written in simple language that anyone can understand and follows a standard format of “As a [user role], I want [functionality], so that [benefit]”. A user story helps to capture the user’s needs and expectations from the system and provides a basis for developing test cases and acceptance criteria. A BA should use user stories to document the functionality that a system should provide so it can be developed into a work item. References: https://trailhead.salesforce.com/en/content/learn/modules/business-analysis-user-stories/write-user-stories