Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
The Salesforce Business Analyst Handbook

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

Arrow left icon
Product type Paperback
Published in Nov 2022
Publisher Packt
ISBN-13 9781801813426
Length 232 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Srini Munagavalasa Srini Munagavalasa
Author Profile Icon Srini Munagavalasa
Srini Munagavalasa
Arrow right icon
View More author details
Toc

Table of Contents (21) Chapters Close

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

Exploring the timing and participants of CRPs

For each of the CRP phases, plan to do two sessions. The first session is done mid-way through the project phase so that users get a chance to see how things are progressing. The second one is done at the end of the phase to get an agreement and approvals. The first session will usually be longer and can consist of 1 to 3 full-day sessions. The second session will usually be shorter. You do not need to plan exactly the same duration for all phases as it depends on your business needs. For example, if the requirements are vague, then the scoping CRPs can run for longer. Similarly, if the design is complex, then the design CRP needs to run for longer. In my case, when we did a PRM release, which is a high-priority company initiative, our first sessions lasted a week, where we invited key stakeholders from various regions to collocate in a full-day conference session. The second session we did was a hybrid model as it was too much for users...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime