The Salesforce Business Analyst Handbook: Proven business analysis techniques and processes for a superior user experience and adoption

This is a 'easy to read', 'easy to understand' book that's well structured to cover all topics that a Salesforce business analyst would need to know. Srini used a plethora of practical use cases to explain the concepts as clearly as possible. Dividing the book into 3 logical parts that a business analyst goes through during a project life cycle makes this much more practical to read. I think this book is a good read for even non-salesforce folks as it talks about a lot of concepts that apply to all technologies in the industry. Highly recommend this book for everyone in the salesforce industry regardless of their role and experience. A book that enriches anyone and everyone that reads it. Wish this came out years ago - highly recommended!

I've spent decades creating requirements for business applications, whether in business process reengineering, digital transformation or as a product manager for enterprise software, over that time I have discovered a lot, made plenty of mistakes and finally honed how I practice into a set of concepts and techniques that work for me. You can do the same... or you can read this book. It's comprehensive, well written and easy to read, the illustrations are clear and useful. If you're working in the Salesforce ecosystem trying to configure the tools to your business, you won't go wrong if you follow this book. If you're not working in Salesforce, reading this book will not be a waste of your time.

As a SF business analyst, I thought I knew enough to support my users. But this book taught me everything else that makes me a more effective and knowledgeable BA. The tone of the book is not preachy, it’s actually easy to read and understand. And I like how the topics are grouped together. This book is a keeper, because I expect to refer to it when necessary in my daily analyst role.

Although it is an OK source of information for inexperienced business analyst and may be helpful for structured thinking related to working with Salesforce, the book is vague and contains sentences like “If you use a CRM such as Salesforce…” which makes you think it wasn’t written as Salesforce-dedicated book at first place. It is not awful though. It is just not Salesforce book and there are better sources of information for Business Analysis as well. If you check further reading section after the chapters, it recommends Wikipedia, PMI guide for business analysts and some best-selling books related to SW development: go for it, don’t buy this book.

The author explains every phase with examples that you can easily relate to in real life. The author also touches on things that are often ignored or forgotten in such initiatives - like identifying Non Functional Requirements.The book does a great job in reminding Analysts to always keep the end user experience in mind even when you are dealing with technical aspects of the implementation. The book will come in handy for all Salesforce Analysts working on an implementation, small or large.

This book was printed for me on Jan 7th? Didn’t know that’s what people are doing these days. I know most of the content in this but have a hard time to remember, so I bought this book for reference. It’s got most information: SDLC, responsibilities, and more.And then 10 days later I lost my job. I am not linking my plight to the book though. It’s a nice book

The book covers - in a great way - methods appropriate for project-based Salesforce deliveries.It allows readers to hone their skills for carrying out key project activities such as gathering requirements in a BRD, carrying out UAT and how to plan user training sessions for initial rollout and major releases.

I guess I was expecting something else. This is pretty basic. I knew all the concepts already.