Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
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

Managing scope creep during CRPs

Planning and conducting many CRPs has its own pros and cons:

  • The pros are that we keep everyone informed and on the same page. By collaborating as a group during the CRP session, participants get an opportunity to progressively see the product (functionality) develop. This helps with having open and honest conversations and helps the team steer in the right direction.
  • The cons are that there is a lot of room for scope creep. Business stakeholders may realize they failed to identify or inform other business needs. This is a good thing as far as the scope of the CRM phase is concerned, as the main goal here is to identify gaps and improvements.

Let us see the impacts of these pros and cons during each stage of CRPs and how we can manage them to our advantage.

During the scope CRP phase, we certainly should expect many requests, and the majority of them are usually valid. What is in scope and what is not in scope needs to be carefully...

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
Banner background image