Book Image

The Salesforce Business Analyst Handbook

By : Srini Munagavalasa
5 (1)
Book Image

The Salesforce Business Analyst Handbook

5 (1)
By: Srini Munagavalasa

Overview of this book

Salesforce business analysis skills are in high demand, and there are scant resources to satisfy this demand. This practical guide for business analysts contains all the tools, techniques, and processes needed to create business value and improve user adoption. The Salesforce Business Analyst Handbook begins with the most crucial element of any business analysis activity: identifying business requirements. You’ll learn how to use tacit business analysis and Salesforce system analysis skills to rank and stack all requirements as well as get buy-in from stakeholders. Once you understand the requirements, you’ll work on transforming them into working software via prototyping, mockups, and wireframing. But what good is a product if the customer cannot use it? To help you achieve that, this book will discuss various testing strategies and show you how to tailor testing scenarios that align with business requirements documents. Toward the end, you’ll find out how to create easy-to-use training material for your customers and focus on post-production support – one of the most critical phases. Your customers will stay with you if you support them when they need it! By the end of this Salesforce book, you’ll be able to successfully navigate every phase of a project and confidently apply your new knowledge in your own Salesforce implementations.
Table of Contents (21 chapters)
1
Part 1: Planning and Analysis – BRD/Prioritized Product Backlog
7
Part 2: Design, Development, and Testing – Iterative Cycles with Prototypes and Conference Room Pilots
13
Part 3: End User Testing, Communication, Training, and Support

Elicitation and Document Requirements

In the previous chapter, you did all the planning in identifying the sources from which you can elicit the business needs. In this chapter, we will discuss various methods to draw out those needs and requirements from various sources. We will dive deep into various sources and you will learn a few cool tips that you can implement during your elicitation phase. Our end goal here is to extract sufficient information to understand users’ requirements.

We will also look into best practices to efficiently and effectively document these requirements. As we process elicitation iteratively, we document them right from the start and we keep refining them as we understand them more and more. Our goal here is to document all requirements – needs, wants, nice to haves, and assumptions – and come up with a solid list of all requirements that can be understood by stakeholders. Requirement elicitation is an iterative loop: you plan, prepare...