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

Practical tips for success

A few practical tips that can be of benefit during your CRP sessions are as follows:

  • Use templates: Standardize and use the same format for all your CRPs, for example, Agenda, PowerPoint Deck, or an issues/enhancement tracker. This helps participants get comfortable with processes and procedures.
  • Communication with stakeholders and project team members: Send status reports periodically with action items and due dates to all participants and possibly include their managers and other project team members who are not at the meeting. Make all artifacts available (a read-only version) on a central document management system that team members can access, such as a SharePoint/Teams site or a document management tool of your choice.
  • Engage leads: Always make it a point to engage leads so that resources assigned to the project are completely motivated for the entire duration of the session. Also, provide feedback, especially where positive, to respective...