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

Types of testing

Let us review some important testing types in the context of SaaS CRM implementations.

We will focus on testing related to SaaS model software. With SaaS providers such as Salesforce, HubSpot, or NetSuite, we do not need to worry much about performance, scalability, and security issues if we follow the software provider’s guidelines and best practices.

There are two main types of testing that we are interested in in this chapter:

  • Functional testing: This is a software testing technique to test the features and functionality of the developed solution. Functional testing includes positive, negative, and boundary scenarios. Let us look at some common functional testing techniques:
    • Unit testing (also called development unit testing): Unit testing is done by the technical team member on individual units/modules to determine whether there are any bugs in the code. Following the unit test life cycle, a unit test helps with identifying issues early and...