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 End-to-End Implementation Handbook

You're reading from   Salesforce End-to-End Implementation Handbook A practitioner's guide for setting up programs and projects to deliver superior business outcomes

Arrow left icon
Product type Paperback
Published in Mar 2023
Publisher Packt
ISBN-13 9781804613221
Length 302 pages
Edition 1st Edition
Languages
Concepts
Arrow right icon
Author (1):
Arrow left icon
Kristian Margaryan Jørgen Kristian Margaryan Jørgen
Author Profile Icon Kristian Margaryan Jørgen
Kristian Margaryan Jørgen
Arrow right icon
View More author details
Toc

Table of Contents (21) Chapters Close

Preface 1. Part 1:The Pre-Development Phase
2. Chapter 1: Creating a Vision for Your Salesforce Project FREE CHAPTER 3. Chapter 2: Defining the Nature of Your Salesforce Project 4. Chapter 3: Determining How to Deliver Your Salesforce Project 5. Chapter 4: Securing Funding and Engaging with Salesforce and Implementation Partners 6. Chapter 5: Common Issues to Avoid in the Pre-Development Phase 7. Part 2: The Development Phase
8. Chapter 6: Detailing the Scope and Design of Your Initial Release 9. Chapter 7: Building and Testing Your Initial Release 10. Chapter 8: Common Issues to Avoid in the Development Phase 11. Part 3: The Roll-Out Phase
12. Chapter 9: Deploying Your Release and Migrating Data to Production 13. Chapter 10: Communicating, Training, and Supporting to Drive Adoption 14. Chapter 11: Common Issues to Avoid in the Roll-Out Phase 15. Part 4: The Continuous Improvement Phase
16. Chapter 12: Evolving Your Salesforce Org and DevOps Capabilities 17. Chapter 13: Managing Your Salesforce Data to Harvest the Fruits of Customer 360 18. Chapter 14: Common Issues to Avoid in the Continuous Improvement Phase 19. Index 20. Other Books You May Enjoy

Establishing your development process

One of the key components of the development process is the sprint. A sprint is a term used in Scrum to describe a predefined duration in which the aim is to develop working software. We have already mentioned that a sprint’s duration is not set in stone – it can be decided that it will last anywhere from 1-4 weeks. Let’s look at what you should consider when determining your sprint duration:

  • Will user stories need refinement during the sprints?
    • If yes, this will take time away from development. Having a short (1-2 weeks) sprint duration will impact the expected sprint efficiency beyond what is sensible, as the overhead for refinement and agile ceremonies is greater than the available time for development. If you need continuous backlog refinement sessions, increase your sprint duration.
    • If no, meaning you have already refined and provided solutions to your user stories upfront, then you may opt for a shorter sprint duration...
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