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 2 - Elicitation and Document Requirements

  1. For a medium-complexity functionality, you do it about three times:
    • The first round to understand current processes (automatic or manual) and high-level business needs
    • The second round to dig deep using tools and techniques to probe further to closely understand the real needs
    • The third round to refine your understanding and document them at a high level, review, adjust, and get consensus.
  2. The most important tasks are to be able to extract and understand:
    • Known knowns: These are easy to identify. Get as much detail as possible.
    • Known unknowns: The users do not know these clearly; you can help get to them by using various elicitation techniques.
    • Unknown unknowns: The users do not know what they want. They may not even know if they really want it. You can use techniques such as wireframes/prototypes to understand these unknowns.
  3. If you diligently follow these tasks, you will be well prepared for effective and productive elicitation...