You're reading from Salesforce End-to-End Implementation Handbook

Product type Book

Published in Mar 2023

Publisher Packt

ISBN-13 9781804613221

Pages 302 pages

Edition 1st Edition

Languages

Apex

Concepts

CRM

Author (1):

Kristian Margaryan Jørgensen

Table of Contents (21) Chapters

Preface

1. Part 1:The Pre-Development Phase

2. Chapter 1: Creating a Vision for Your Salesforce Project

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

Why subscribe?

20. Other Books You May Enjoy

Choosing your delivery methodology

In the previous chapter, you defined the nature of your Salesforce project – the desired business capabilities, and the high-level hypothetical technical scope. As illustrated in the following figure, it is now time to determine how to deliver your Salesforce project.

Figure 3.1 – Activities in the pre-development phase

Before jumping to delivery methodologies, let’s briefly look at what is special about enterprise projects, and Salesforce projects in particular.

Enterprise projects

Considering all the types of projects an organization may be planning or currently delivering, it is important to note the differences between them.

The following table provides a simple overview of the nuances between some of the most common enterprise project types:

The rest of the chapter is locked

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

Start free trial

Renews at €14.99/month. Cancel anytime}

Authors (1)

Kristian Margaryan Jørgensen

Kristian Margaryan Jørgensen is a Salesforce Solution Architect at Waeg, an IBM company, with nearly a decade of combined Salesforce end-user, consultant, and solution architect experience. His experience from both the customer-side and consulting-side of implementations enables him to empathize when advising and challenging enterprise customers on how to plan, orchestrate, and scale their Salesforce implementations with clear focus on usability, scalability, and adoption to succeed in unlocking value from their Salesforce investments. Kristian holds 14 Salesforce certifications including Strategy Designer, Development Lifecycle and Deployment Architect as well as Application Architect, and System Architect. He is a certified SAFe Agilist.

See other products by Kristian Margaryan Jørgensen