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

Understanding what CRPs are

CRPs are workshops where key stakeholders, along with project team members, collaborate at various stages of projects to understand the business needs while transforming them into proposed business solutions. CRPs help stakeholders collaborate and see how their needs progress through each phase of the project, as well as being able to provide feedback. This helps users see what they are getting and keep the process transparent. Also, these CRP sessions help the technical team and testing team understand the needs better, so they will be able to deliver what the business truly wants.

Based on the complexity of the business requirements, the project team can decide when to do CRP and how often to do the CRP sessions. As a rule of thumb, I prefer to go with three CRP stages for a project with medium to high complexity and maybe a fourth one if the project is highly visible and critical or highly critical.

The four stages when we conduct the CRPs are as...