You're reading from The Salesforce Business Analyst Handbook Proven business analysis techniques and processes for a superior user experience and adoption

Product type Paperback

Published in Nov 2022

Publisher Packt

ISBN-13 9781801813426

Length 232 pages

Edition 1st Edition

Tools

Salesforce

Concepts

Business Process Management

Author (1):

Srini Munagavalasa

Preface

1. Part 1: Planning and Analysis – BRD/Prioritized Product Backlog

2. Chapter 1: Identifying Requirements FREE CHAPTER

3. Chapter 2: Elicitation and Document Requirements

4. Chapter 3: Prioritizing Requirements

5. Chapter 4: Process Flows – “As-Is” versus “To-Be”

6. Chapter 5: Business Requirements Document

7. Part 2: Design, Development, and Testing – Iterative Cycles with Prototypes and Conference Room Pilots

8. Chapter 6: Solution Design and Functional Document

9. Chapter 7: Demonstrate Functionality Using Prototypes

10. Chapter 8: Exploring Conference Room Pilots

11. Chapter 9: Technical and Quality Testing

12. Chapter 10: Requirements Traceability Matrix

13. Part 3: End User Testing, Communication, Training, and Support

14. Chapter 11: User Acceptance Testing

15. Chapter 12: Communication and Knowledge Management

16. Chapter 13: End User Training

17. Chapter 14: Post Go-Live Support / User Forums

18. Assessments

19. Index

20. Other Books You May Enjoy

Reviewing the benefits of UAT

There are several benefits to UAT. I will list a few that I found useful:

Business users get a chance to verify and validate that the software functionality meets the business requirements. In addition to identifying defects, it helps the project get feedback and suggestions from business users. The project team can decide on whether to incorporate the requests in the same release or a future release based on impact assessment.
This is our last and only chance to find defects before deploying to the production environment and thus reduce risk. Being knowledgeable about the testing process, they can find it fast and be able to explain how, when, why, and where they found the defect so that it can be reproduced and fixed faster. If this defect is missed during testing, it may result in different end users from different departments experiencing the same issues after deployment to production. The same issues may be described in different ways...