Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Salesforce End-to-End Implementation Handbook
  • Table Of Contents Toc
  • Feedback & Rating feedback
Salesforce End-to-End Implementation Handbook

Salesforce End-to-End Implementation Handbook

By : Kristian Margaryan Jørgensen, Kristian Margaryan Jørgen
4.9 (13)
close
close
Salesforce End-to-End Implementation Handbook

Salesforce End-to-End Implementation Handbook

4.9 (13)
By: Kristian Margaryan Jørgensen, Kristian Margaryan Jørgen

Overview of this book

With ever-growing digital transformation programs involving Salesforce, there is a greater need for a comprehensive overview of the phases and activities specific to Salesforce implementations. This book will act as a detailed guide for your Salesforce implementation journey, including common issues and pitfalls to mitigate and prevent errors. The Salesforce End-to-End Implementation Handbook starts with the pre-development phase. Here you’ll understand how to define the vision and nature of your project, determine your change management strategy and delivery methodology, learn to build a business case for your project, get insights on engaging with Salesforce and implementation partners, and learn to establish a governance framework. As you progress, you’ll gain insights on the necessary activities, milestones, and common issues faced in Salesforce implementation, along with strategies to mitigate them. At the end of each section, you’ll find evaluation checklists to assess the state of your Salesforce implementation. By the end of this book, you’ll be well-equipped to set up Salesforce projects and programs effectively and deliver maximum ROI.
Table of Contents (21 chapters)
close
close
1
Part 1:The Pre-Development Phase
7
Part 2: The Development Phase
11
Part 3: The Roll-Out Phase
15
Part 4: The Continuous Improvement Phase

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

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech

Create a Note

Modal Close icon
You need to login to use this feature.
notes
bookmark search playlist font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY