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

View More author details

Table of Contents (21) Chapters

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

Why subscribe?

20. Other Books You May Enjoy

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...