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

Listed here are a few tips that are specifically useful during requirements documentation:

Collaboration: You need to work with the technical lead, architects, lead developer, QA lead, and training team members to prepare this document. Their input is very much needed to capture various attributes, such as alternative flow and system response. This collaborative team will help to identify business context-related missed requirements. You need to adopt an iterative approach and need tight collaboration so that the team members are comfortable with what is documented. They are the main consumers of this document. Once the document is finalized and agreed upon by this team, socialize the final version with key stakeholders, walk them through it line by line, and get agreement and approval.
Visual artifacts: Utilize any flow charts and screen mockups created during prior phases while documenting the BRD. This will help to keep the team focused on...