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

The need for prototyping and its categories

A prototype is a mock-up, or a model, of an idea based on the business needs that team members can develop, interact with, and provide feedback on. A prototype can just be a static model or can be a limited functionality model and provide a way to visualize the proposed design solution beforehand. This idea is developed iteratively and organically with input and feedback from key team members and helps us move in the right direction. Building and socializing prototypes helps us see abstract ideas in a solid form where users can visualize them, concur, and confirm or reject them. We basically get all the associated team members on the same page and a greater understanding of the idea can be put into action. In some cases, the user who defined the business need or requirement may not really want the prototype solution at all or may want it to be different. Prototyping an activity responds to actual user needs by helping the users understand...