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

Post Go-Live Support / User Forums

In the previous chapter, we successfully completed our end user training. With this, we have completed all the project activities and got the go-ahead to go live with the new functionality. Our team did a phenomenal job right from understanding business requirements to developing and deploying a great solution that meets the business needs. We took our time, planned, and executed training, and made sure the team was aware of new features and functions. We also made sure that they were upskilled with all the tools and tricks on how to navigate and use the system. Finally, the day we were waiting for arrived and we implemented and deployed the new system (features and functions), which enabled access to the software system for our users.

Now, what next?

I have seen many projects celebrate and disband the project team within a week or two after going live. This is where all the problems start. For users to get adjusted to the system functionality...