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

Exploring types of traceability

There are three types of traceability. We move from left to right, right to left, or either way. They are as follows:

  • Forward traceability: We start with a prioritized requirement and trace it each way to see the design, development, and testing progress in the right direction toward our proposed and intended functionality. Essentially, it helps us to make sure that we captured the requirement correctly, we have all the information related to the requirement, and that this is the right requirement.
  • Backward traceability: We start tracing backward from specific phases of projects. It can be from test script to development to design to the business requirement, or it can be from solution design to functional design to business requirement. This is to make sure we are doing the right thing and staying on the right track and not going off course. This type of traceability ensures that we should be able to trace each individual functionality...