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

Planning testing activities

Software testing should be planned well in advance and the testing team should be involved from the start of the project. On any type of project, we cannot do exhaustive testing and test everything in all possible combinations as it is practically not feasible. Planning helps us make educated choices and make the testing sensible and meaningful. The testing plan is a progressive document and gets refined during the entire course of the project, starting from the requirements phase and getting more granular and refined as we progress.

Let us look at what tests need to be planned during various project phases:

  • User Acceptance Testing (UAT) planning is done during the requirements specification phase. This test plan outlines what the business users may possibly be testing during the acceptance phase of testing. This UAT plan incrementally gets updated as it helps us with the finalized UAT plan with relevant scope and scenarios.
  • System Integration...