Search icon CANCEL
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
Salesforce Sales Cloud – An Implementation Handbook

You're reading from   Salesforce Sales Cloud – An Implementation Handbook A practical guide from design to deployment for driving success in sales

Arrow left icon
Product type Paperback
Published in Apr 2024
Publisher Packt
ISBN-13 9781804619643
Length 368 pages
Edition 1st Edition
Concepts
Arrow right icon
Author (1):
Arrow left icon
Kerry Townsend Kerry Townsend
Author Profile Icon Kerry Townsend
Kerry Townsend
Arrow right icon
View More author details
Toc

Table of Contents (20) Chapters Close

Preface 1. Part 1:Building the Fundamentals
2. Chapter 1: Preparing for Success FREE CHAPTER 3. Chapter 2: Defining the Approach 4. Chapter 3: Design and Build: The Core Sales Process 5. Chapter 4: Design and Build: The Lead Generation Process 6. Chapter 5: Design and Build: Sales User Productivity 7. Part 2: Preparing to Release
8. Chapter 6: Bringing Data into Sales Cloud 9. Chapter 7: Getting Sign-Off 10. Chapter 8: Executing Testing 11. Chapter 9: Executing Training 12. Chapter 10: Deployment Planning 13. Part 3: Beyond the Fundamentals
14. Chapter 11: Territory Management 15. Chapter 12: Modeling Additional Processes with Sales Cloud 16. Chapter 13: Common System Integrations 17. Chapter 14: Extending with the AppExchange 18. Index 19. Other Books You May Enjoy

The impact of deployment methodology and environment strategy on testing

In the previous sections, we explored common development methodologies and the environment strategy that’s used for Sales Cloud projects. The approach taken here has an impact on how testing can be incorporated into the development life cycle. Let’s explore how each has an impact:

  • Development methodology: Agile and Waterfall require different testing skills. The difference between working with an Agile, rather than Waterfall, methodology is that the focus is on face-to-face communication rather than extensive documentation. This means there is less documentation for testers to work from. Documentation is required. Agile can be harder for testers as there is a need to continuously adapt. Testers on Agile projects fulfill a range of roles, including attending sprint planning, estimating tests, writing test cases, and attending reviews.
  • Environment strategy and management: Not having dedicated...
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 €18.99/month. Cancel anytime