fbpx

Salesforce Business Analyst | Certification Guide

The Salesforce Business Analyst Certification is developed for Business Analysts with Salesforce experience. Candidates should have knowledge, skills, and experience on driving business improvements through the Salesforce platform, with an understanding of business needs, implementing business analysis activities, and collaborating with stakeholders.

Key Facts

The exam is made up of 60 multiple choice questions

105 minutes to complete

The passing score is 72%

The pre-requisite is a Salesforce Certified Administrator credential.

Cost is USD $200 and the retake fee is is USD $100 if you are unsuccessful

This guide will explain everything that test takers need to think about how to become a Salesforce Business Analyst-certified and the core topics of the exam.

There are 6 areas of knowledge that are covered by the Salesforce Business Analyst certification.

They are covered by the Business Analyst training, but if you are not able to attend, then you will need to ensure you know the areas listed below well.

Objective

Weighting

Customer Discovery

17%

Collaboration with Stakeholders

24%

Business Process Mapping

16%

Requirements

17%

User Stories

18%

User Acceptance

8%

Business Analyst Topic Weighting Chart

Business Analyst
Certification Contents

The following are the core topic areas of the Salesforce Business Analyst certification and what you’re expected to know:

Customer Discovery

This topic includes the following objectives:

  • Determine business strategies, goals, initiatives, and challenges to define the scope of business analysis.

Discover customer needs using various methods and strategies to determine customer challenges, share those insights with your customers, and identify opportunities for ways they can improve how they work. By understanding your customer, their business, and any obstacles to the project, the business analyst co-creates, alongside of your customers, successful strategies to address their needs.

  • Discover how a customer is leveraging and benefiting from Salesforce products to establish the current state.

Using empathic research, the business analyst must first thoroughly understand the current state of the customer’s operations and how they are using Salesforce. A detailed understanding of what is and isn’t working today is critical to the success of suggesting future state improvements.

  • Understand and explain Business Analyst roles and responsibilities in different phases of the implementation lifecycle.

As the business analyst performs different tasks and roles throughout the implementation, understanding what is required at which stage is important to successful implementations. From requirements gathering to creating documentation to performing project management duties to achieving a successful rollout, the business analyst needs to understand what those roles and responsibilities are at all stages of the implementation lifecycle. Additionally, the business analyst must possess the following skills: Writing, ability to ask questions to elicit needs, perform analysis of data, recommend and implement solutions.

  • Apply the implementation lifecycle for planning business analysis activities.

To create a successful implementation, the business analyst must understand the implementation lifecycle, including managing various releases throughout the development phase. The business analyst should be able to use the various development models to manage deployments. 

  • Analyze the customer's Salesforce environment to identify opportunities and constraints.

To successfully implement solutions that meet customer’s needs, the business analyst should proactively analyze the customer’s Salesforce environments to check the health of those environments, as well as identify any constraints they must work within when suggesting improvements. The business analyst should be able to maintain and improve those environments using tools that are built into Salesforce as well as identifying tools available on the AppExchange.

  • Demonstrate knowledge of Salesforce capabilities and its potential to recommend solutions to the business.

The business analyst must use their knowledge of the Salesforce platform, both its capabilities and limitations, to recommend solutions that will work to meet the stakeholders’ business needs. Knowledge of the Salesforce connected ecosystem, Salesforce 360, its benefits and how it can be used throughout an organization, is critical to being able to recommend appropriate solutions to meet the needs of the various stakeholders.

Customer Experience

Collaboration with Stakeholders

This topic includes the following objectives:

  • Plan discovery activities based on the target stakeholders to perform a thorough analysis of business needs.

Understand the various stakeholders a business analyst works with and the methods of engagement required to effectively collaborate with each. Use appropriate tools at every stage of the engagement to ensure that the information collected is accurate and complete.  Ability to draft appropriate documentation needed to write requirements, create buy-in, confirm alignment and ensure transparency throughout the engagement.

  • Identify key stakeholders and develop relationships with them as a trusted advisor to act as a liaison between business and technical teams.

Identify stakeholders a business analyst works with and the required methods of communication when working with each. The Business Analyst must understand how to build and maintain a positive relationship with all the stakeholders to ensure a successful engagement from start to finish – from requirements gathering to diagramming those requirements and ensuring that the stakeholders understand and see the value of the recommendations the business analyst makes. A good business analyst knows how to advocate for their customers.

  • Given a scenario, choose the most effective technique for eliciting business needs from stakeholders.

Ability to use a variety of tools and methods to understand and document the current and desired states. Use the appropriate method to elicit needs and impediments to achieving those needs. The business analyst needs to be able to create a safe environment where stakeholders feel understood and heard and are willing to collaborate, as elicitation is one of the most important stages of any project which sets the basis for everything that follows. The business analyst should understand and use all the tools available to ensure that elicitation is detailed, accurate, and complete.

  • Explain how to move from current state analysis to an agreed future state design.

Understand the various analysis tools used to identify the differences between the current and future states and any impediments to achieving the future state. Identify any barriers or limitations to achieving the future state, and ensure that any suggested improvements and recommendations are feasible based on barriers or limitations that cannot be overcome.

  • Understand how Salesforce features and best practices impact solution options and business processes.

A business analyst should have a thorough understanding of Salesforce 360 and the features and benefits of the platform, clouds, tools, and applications it offers, along with the ability to effectively use the AppExchange. The business analyst uses their knowledge and experience to recommend the best approach for any project, based upon the requirements of that project.

  • Given a scenario, manage competing priorities to obtain sign-off from stakeholders.

As a business analyst, managing the project from start to finish requires managing multiple and sometimes conflicting priorities of different stakeholders, which is often a challenge.  The business analyst should have a thorough understanding of the skills, tools, and methods needed to help manage and limit delays, changing priorities, scope creep, and disagreement between stakeholders.

CRM workflow tools

Business Process Mapping

This topic includes the following objectives:

  • Demonstrate how to define the scope of a complex business process and break it down into manageable steps.

The business analyst should know the various mapping tools available and when each is best used to document a process to communicate the data therein with the stakeholders. Process mapping also helps the business analyst understand the process in detail, which helps the business analyst during the analysis phase.

  • Apply understanding of hierarchical process mapping to engage stakeholders at different levels of an organization.

The business analyst must create and deploy several process mapping tools to provide multiple levels of detail to a varied stakeholder audience, ensuring that all team members understand both current and future states.

  • Analyze and document a business process to elicit requirements and identify resources to visualize a future state.

The business analyst must understand the various process mapping tools to identify which should be used to convey the desired information, as different maps display information in different ways, based on the process being mapped. The business analyst should be able to state which process map is appropriate for the process to be mapped and understand that different maps may be required before analysis can begin.

  • Apply governance on agreed future state processes to control scope.

Understand the governance framework within an organization. Utilize the specific roles and responsibilities identified within that framework and how that can be of benefit to the business analyst throughout the life of the project.

Salesforce Javascript Developer I - Browser and Events

Requirements

This topic includes the following objectives:

  • Distinguish between requirements vs. user stories to engage business and technical stakeholders.

Document requirements clearly and concisely following the V2MOM process. Use the documented format for writing user stories when documenting requirements. Explain why stakeholder alignment is important to successful completion of any project as well as the ramifications, should alignment not be given and maintained. Use documentation to gain and maintain stakeholder alignment.

  • Verify and prioritize existing requirements and identify new requirements to develop the future state.

Explain the Agile framework of system development using both Scrum and Kanban workflows. The Business analyst should be able to define the Scrum and Kanban workflows and when each would benefit a project, so they can use the appropriate workflow based on the project’s circumstances.

  • Document requirements in a version controlled repository to manage scope.


Explain the purpose of a version control system (VCS) is and how it benefits project teams. State what project aspects are stored in a VCS. Illustrate how a VCS impacts the development lifecycle. Understand the differences between a central VCS and a distributed VCS. Explain the benefits of using a VCS in projects.

CRM Business Tools and Processes

User Stories

This topic includes the following objectives:

  • Understand the components of a user story to perform thorough analysis.

Explain the parts of a user story. Explain the differences between a persona and archetype and how they relate to user stories. Able to write appropriate user stories based on the requirements. Explain what makes a good vs poor user story. State what should not be included in a user story.

  • Contrast the difference between acceptance criteria vs. definition of done.

Understand and explain the differences between acceptance criteria and the definition of done and why this matters for a project. Understand what goes into creating good acceptance criteria and the ability to draft well-written acceptance criteria. State how acceptance criteria relates to user stories. Define the definition of done. Explain how the definition of done fits into the development framework.

  • Document user stories in a version controlled repository to manage scope.

Understand the benefit of maintaining version-controlled project documentation. State how version-controlled documentation impacts team collaboration. Explain the best place to store project documentation.

User Acceptance

This topic includes the following objectives:

  • Define and prepare the User Acceptance Test plan to confirm the solution meets the business requirements.

Explain the purpose of user acceptance testing (UAT). Define the people who should be involved in UAT. Explain best practices when planning for UAT. Create test plans including: drafting the scripts, assigning the appropriate users to perform the testing, and who will be approvers once the plan is executed. Understand the various decision scenarios of what should happen when UAT is complete and the business analyst's role in making those decisions.

  • Guide UAT and manage the results to determine whether the solution meets the requirements.

Understand what needs to be done prior to beginning UAT). Schedule and execute the testing using stakeholder-approved test plans. Define the test parameters and ensure that testers understand their roles and responsibilities as they are executing the test plans. Plan and conduct meetings related to the UAT phase. Understand how to close the UAT phase.

  • Given a scenario, make a go/no-go release decision when new business or technical issues arise.

Explain the decision making process required to determine whether or not to deploy new functionality based on the UAT feedback. Understand the options available when making go-live decisions.

Features of Apex


To prepare successfully for the certification exam, we recommend to work through our

Business Analyst Study Guide and Business Analyst Practice Exams

Business Analyst
Study Guide

Every topic objective explained thoroughly.
The most efficient way to study the key concepts in the exam.



Business Analyst

Practice Exams

Test yourself with complete practice exams or focus on a particular topic with the topic exams. Find out if you are ready for the exam.


Copyright 2022 -  www.FocusOnForce.com

Copyright 2019 -  www.FocusOnForce.com

@

Not recently active