Delivering Successful Salesforce Projects

The sales process gives insights on the reasons why a project is initiated in the first place and a view point from both the customer and consultant.

The project handover describes best practice actions for a customer and a consultant to do when they handover a project Statement of Work to the team who will be delivering the outcomes.

After this chapter you will have learnt about the Change Curve and how people are affected by change from a project. You will also learn about Prosci Adkar, a method to implement successful change practices.

This chapter will cover the different types of stakeholders who are affected by a project delivery and the use of RACI to define their roles and responsibilities.

This chapter covers the qualities of a good manager and how they, using a formula, can create and nurture a high performing team.

This chapter covers the main project methodologies that can be used for delivery and how a blended approach can be an effective alternative.

This chapter looks at different communication options and how they might be used during a project in terms of their audience, content and cadence.

Here are some tips for the student to consider how to manage the situation when things go wrong in a project.

This chapter covers the prospect of risk in a project, its definition, how to track them and the types that might affect a successful project delivery.

This chapter covers the tasks and considerations for preparations of a project kick off.

The student will learn how to deliver a collaborative project kick off so to engage all their stakeholders.

This chapter talks about the different techniques that Business Analysts use to illicit information from stakeholders, how to capture requirements with note taking and process map building.

The students will learn about Gherkin language to construct user stories to help define the requirement.

This chapter talks about the many elephants in the room in regards to a project.

The student will learn about the different tools that can be used to help capture user stories and track their progress over the course of the project.

This section informs the student about solution design resources available for Salesforce project delivery.

This chapter reminds the student about the problems and power of making assumptions in a project.

This chapter explains the different ways to estimate a project delivery in terms of time, effort, size and dependencies.

This chapter will help the student how to plan their sprint activities.

The student will learn there are build theories and standards to consider when delivering Salesforce software projects.

This chapter talks about delivering demos to customer's, known as Show and Tells and their benefits.

The student will learn about the importance of developing a Trusted Advisor role with the customer and the steps to get there.

This chapter talks about the ethos of the quality triangle and how project delivery need to be a fine balance of these elements.

The student will learn how the power of saying no is sometimes a necessary thing during a project.

This chapter looks at change requests and when to use them during a project.

The student will learn about the role of the quality assurance team in a project.

The student will learn the benefits of system integration testing as part of project delivery.

The student will learn the importance of user acceptance testing and its sign off as part of the project.

This chapter covers how to prepare and deliver training to end users.

The student will be given tips on factors to consider for deployment during a project.

This chapter focuses on the importance of data migration as a project deliverable.

The student will learn about different aspects of documentation that need to be considered during a project.

This chapter looks at the steps of a go live scenario.

The student will learn the tips for a smooth handover post go live.

The student will learn about he importance of project reflection with lessons learnt and retrospectives.

This chapter highlights that it is important to celebrate a delivery as usually so much happens during a project.

This chapter talks about the various elements of adoption of a new systems for end users and admins.

The student will learn that with software delivery there will often be future iterations.

The student will learn about Theory of Cake and the theme behind this whole course.

The last chapter to say thanks for watching and hoping students have learnt something about delivering successful Salesforce projects.