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

Practical tips for success

A few practical tips that can benefit you during your testing activities are the following:

Do not skip the test strategy. Make a checklist for the test strategy.
Where possible, use automated tools, especially for SIT and regression tests. Regression tests must be run multiple times whenever an issue is fixed.
UAT should be done by business users who are SMEs in their area. Following prior documented test scripts is very ineffective. In addition to test scripts, business users should run through ad hoc real-life scenarios. If there are any issues, this is our last opportunity to find and fix them.
The QA team or SIT team should be made up of independent team members with good system knowledge with some level of business domain knowledge. The technical team members who developed the application should be the last people to do SIT.
Team members should take static testing seriously. A review of the static artifacts by SMEs and leads...