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

Chapter 5 - Business Requirements Document

  1. There are four main types of requirements:
    • Business requirements
    • User requirements (also called stakeholder requirements)
    • Solution requirements (functional and non-functional requirements)
    • Transition requirements
  2. Transition requirements are important as they ensure business continuity and are very critical for a project’s success. Examples include data conversions and end user training requirements.

Think of a scenario where you are migrating from a legacy system to a new cloud-based system; you need to plan to migrate legacy data to the cloud. This migrated data should be usable, and users should be able to create and complete transactions effectively.

  1. Past project documents such as BRDs, Functional Specification Documents (FSDs), and test scripts/scenarios. The majority of the non-functional requirements can be identified from these artifacts. If your implementation is brand new, refer to best practices or blogs...