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 the need for UAT

We have done so many types of testing – unit testing, systems integration testing, and regression testing. Why one more type of testing? Because this is the only time the business users and the end users will be playing with a production-like system with all the functionality and data. UAT is the last available window for us to make sure that the business requirements are designed, solved, and developed to meet the proposed functional solution. It’s not only the functionality but also the look and feel of the screens and the simplicity and ease of navigation for the end user for which we can get feedback.

UAT ensures that we vet out and simulate as many scenarios as possible so that the end users will not face the same issues. One critical issue on a large-scale project can impact thousands of users and this can result in wasted time, resources, and frustrated users.

So, what do we do? Do we just take the SIT scripts and SIT plan and implement...