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

Reviewing the process flow

A process flow is a workflow diagram of all the tasks/steps and their interconnection in a visual format. Depicting various steps in a process visually will help all stakeholders get a common understanding of the needs and, hence, the requirements.

Defining process flows is iterative: you start from the elicitation phase with very high-level process flows and keep refining during the prioritization phase until they are socialized and agreed upon by the stakeholders, SMEs, and technical team members. This business process flow will capture enough details in business terminology so that it is a process flow that all stakeholders understand. During the design and development phase, these flows can be refined so that the technical team and testing team can understand them in greater depth. The first thing we must do when we develop a process flow is have the right set of stakeholders and SMEs with in-depth knowledge of their current process. We do not invite...