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

Planning your build phase

In a pure agile delivery methodology, the team plans their work continuously – either in sprint planning (Scrum) or by simply starting new work when new user stories meet the definition of ready and there is the capacity for it to be picked up (Kanban).

However, having chosen a form of hybrid agile delivery methodology, you’ll likely want to have some indication of the estimated duration of the build phase – both for budgeting and roll-out planning purposes.

In this section, we’ll discuss the advantages and disadvantages of various methods of estimating development effort and how you can plan development.

Let’s look at two methods of estimating effort:

  • Estimating development effort in time format:
    • In the previous chapter, you broke down the overall scope into user stories and provided solutions for each of them. If you didn’t, go back and review this process.
    • To know the total number of estimated development...
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