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

Managing scope creep during CRPs

Planning and conducting many CRPs has its own pros and cons:

  • The pros are that we keep everyone informed and on the same page. By collaborating as a group during the CRP session, participants get an opportunity to progressively see the product (functionality) develop. This helps with having open and honest conversations and helps the team steer in the right direction.
  • The cons are that there is a lot of room for scope creep. Business stakeholders may realize they failed to identify or inform other business needs. This is a good thing as far as the scope of the CRM phase is concerned, as the main goal here is to identify gaps and improvements.

Let us see the impacts of these pros and cons during each stage of CRPs and how we can manage them to our advantage.

During the scope CRP phase, we certainly should expect many requests, and the majority of them are usually valid. What is in scope and what is not in scope needs to be carefully...