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

Summary

In this chapter, we covered techniques that you can use to help you prioritize your requirements so that you can accurately capture business needs in the right order of priority, keeping the process transparent for all stakeholders.

You got a good idea of why requirement prioritization is important and how it helps you to identify the most important requirements that the team should address to fulfill the business need and add value. We looked at various prioritization techniques that can be used to enable the team with the prioritization process. We also showed you how to create a dependency roadmap of requirements to help you identify any gaps and opportunities to improve by adding new requirements or re-arranging existing requirements. Finally, we learned about managing prioritization meetings and getting consensus, helping you to manage conflicts, obtain consensus from all participants, and keep stakeholders up to date with the requirement priorities.

In the next...