Certified-Business-Analyst Reviews Questions

The business analyst should set up a casual meeting to create a personal connection with the stakeholder to build trust with them as the project continues. A casual meeting is an informal conversation that allows the business analyst and the stakeholder to get to know each other better, share their backgrounds and interests, and establish rapport and empathy. A casual meeting can help to ease any tension or frustration that may have arisen during the discovery session, as well as show respect and appreciation for the stakeholder’s input and feedback. References: https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/stakeholder-management

This answer points out that the previous VP’s requirements may differ from those of the new executive as the largest risk with this approach of using the inherited requirements in lieu of a traditional discovery process for a Sales Cloud implementation. Requirements are statements that describe what a solution must do or have to meet the needs and expectations of the stakeholders or users. Requirements may change over time due to various factors, such as business goals, market trends, customer feedback, or stakeholder preferences. Using the previous VP’s requirements without validating them with the new executive may result in a solution that does not align with their vision, strategy, or value proposition. References: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-user-stories-to-capture-requirements

Kanban is an agile methodology that focuses on visualizing work, limiting work in progress, managing flow, making policies explicit, implementing feedback loops, improving collaboratively, evolving experimentally (Kaizen). Kanban is suitable for scenarios where work is generally project-based and can be broken into smaller pieces that can be completed quickly and independently by different team members without dependencies or bottlenecks. Kanban uses boards with columns representing different stages of work (such as backlog, doing, done) and cards representing individual work items (such as tasks, features, bugs). Kanban helps teams monitor their progress, identify issues, prioritize work, optimize resources, improve quality, reduce waste, increase efficiency, deliver value faster, adapt to changing needs, etc.

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. References: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-stakeholder-engagement-skills