certified-business-analyst Sample Questions & Answers

A user story is not considered 'Ready' for development until it has clear, testable acceptance criteria. These criteria define the specific conditions that must be met for the story to be considered complete from the user's perspective. They remove ambiguity and provide the basis for testing.

For non-technical testers, the BA's most critical role is to remove ambiguity and make the process as easy as possible. Detailed test scripts that outline exact steps to follow (e.g., '1. Create a new Opportunity with Amount > $50,000. 2. Set Stage to 'Negotiation.' 3. Click Save.') and define what the expected outcome should be (e.g., 'The Stage automatically updates to 'Awaiting Approval'') are essential for enabling testers to validate the solution against the requirements effectively.

This is the core distinction. A business requirement states the 'why' from the business perspective (e.g., 'Reduce average case resolution time by 15%'). A functional requirement describes a specific capability the system must have ('what') to help achieve that goal (e.g., 'The system must automatically route high-priority cases to a specialized queue').

A formal scope statement is the primary artifact for defining and agreeing upon project boundaries. It explicitly states what is included and, just as importantly, what is excluded from the project. For a complex implementation like CPQ with competing stakeholder interests and a fixed deadline, a clear, signed-off scope statement is essential to prevent scope creep and manage expectations.

This is the standard, best-practice Salesforce solution for this exact business problem. Sales Processes control the picklist values for the Opportunity Stage field. Record Types tie together different Sales Processes and Page Layouts. This combination allows for distinct stages, fields, and user experiences for each sales channel on the single, standard Opportunity object, which is critical for unified reporting while still allowing for channel-specific forecasting.

Swimlanes are a fundamental element of process mapping (especially in BPMN) specifically designed to delineate responsibilities. Each lane represents a different actor, role, or department (e.g., Marketing, Inside Sales), and the tasks performed by that actor are placed within their lane. This provides an immediate, clear visual of handoffs and responsibilities.

This criterion is testable, specific, and describes a condition of satisfaction (the negative case) from the user's perspective, using the common Given-When-Then format.

This criterion is also testable, specific, and describes the primary condition of satisfaction (the positive case) from the user's perspective.

High-quality requirements must be specific, measurable, achievable, relevant, and time-bound (SMART). The term 'user-friendly' is subjective and cannot be objectively tested. A better requirement would be, 'A new user must be able to create a contact record in under 60 seconds without training.' This is specific and testable.

The BA's role is to act as a facilitator. The immediate action should be to acknowledge the feedback and use the opportunity, while all stakeholders are present, to elicit the details of the missing requirement. This allows for immediate collaboration to incorporate the compliance step and work towards a consensus on a revised process, which is more efficient than scheduling separate meetings.

The primary purpose of a stakeholder map is to analyze stakeholders and categorize them based on factors like their level of influence (power) and level of concern (interest) in the project. This analysis helps the business analyst develop a targeted communication and engagement strategy for each stakeholder group, not to determine the project budget.