• Determine business strategies, goals, initiatives, and challenges to define the scope of business analysis.
• Discover how a customer is leveraging and benefiting from Salesforce products to establish the current state.
• Understand and explain Business Analyst roles and responsibilities in different phases of the implementation lifecycle.
• Apply the implementation lifecycle for planning business analysis activities.
• Analyze the customer's Salesforce environment to identify opportunities and constraints.
• Demonstrate knowledge of Salesforce capabilities and its potential to recommend solutions to the business.

Collaboration with Stakeholders: 24%

• Plan discovery activities based on the target stakeholders to perform a thorough analysis of business needs.
• Identify key stakeholders and develop relationships with them as trusted advisors to act as a liaison between business and technical teams.
• Given a scenario, choose the most effective technique for eliciting business needs from stakeholders.
• Explain how to move from the current state analysis to an agreed future state design.
• Understand how Salesforce features and best practices impact solution options and business processes.
• Given a scenario, manage competing priorities to obtain sign-off from stakeholders. 

Business Process Mapping: 16%

• Demonstrate how to define the scope of a complex business process and break it down into manageable steps.
• Apply an understanding of hierarchical process mapping to engage stakeholders at different levels of an organization.
• Analyze and document a business process to elicit requirements and identify resources to visualize a future state.
• Apply governance at agreed future state processes to control scope. 

Requirements: 17%

• Distinguish between requirements vs. User stories to engage business and technical stakeholders.
• Verify and prioritize existing requirements and identify new requirements to develop the future state.
• Document requirements in a version-controlled repository to manage scope.

User Stories: 18%

• Understand the components of a user story to perform a thorough analysis.
• Contrast the difference between acceptance criteria vs. The definition of done.
• Document user stories in a version-controlled repository to manage scope.

User Acceptance: 8%

• Define and prepare the User Acceptance Test plan to confirm the solution meets the business requirements.
• Guide UAT and manage the results to determine whether the solution meets the requirements.
• Given a scenario, make a go/no-go release decision when new business or technical issues arise.