Name: Salesforce Platform Governance Method By Lee Harding
SKU: 9781484274033
Price: 119.49 AUD
Availability: InStock

Salesforce Platform Governance Method Summary

Salesforce Platform Governance Method: A Guide to Governing Changes, Development, and Enhancements on the Salesforce Platform by Lee Harding

Accelerate your Salesforce implementation to provide benefits to your business more rapidly while maintaining control and improving quality.

Salesforce has become one of the most influential business tools in our modern age. What started as the world's most comprehensive customer relationship management (CRM) system available in the market place has now morphed over the years into an ecosystem of tools and services that enable you to run your entire business platform.

This book gives you a method (a set of governance processes) that provides a complete view of how to govern and manage any Salesforce implementation. It breaks the architectural components of the Salesforce platform into manageable sections, allowing you to navigate and understand how to govern your Salesforce implementation in a consistent manner with an approach that is structured, repeatable, and clearly defined.

Salesforce Platform Governance Method is divided into nine distinct phases which have been chosen based on how the Salesforce platform is architected. This is relevant today because every organization that implements Salesforce will face the same issues around governance, integration, development, and security and the majority of organizations will find, through trial and error, a solution to govern these components. This book will help Salesforce professionals and enterprise organizations as well as small and mid-sized businesses (SMBs) navigate these topics and ultimately have a successful and fully integrated, secure Salesforce implementation.

What You Will Learn

Govern the application architecture on the Salesforce platform, including general architecture, localization and global deployments, workflow and process, formulas and files, and social
Govern the data architecture, including design and data optimization, performance, predictive and actual data volumes, and data movement
Govern the identity and access management aspects of the application and Salesforce platform
Govern the low-level platform capabilities delivered through Lightning, Visualforce, and Apex
Handle community implementations that bring specific features into the Salesforce platform for consideration and governance
Create checklists for the governance steps, laid out in the method, and for any tooling recommendations that can help simplify the process of governance

Who This Book Is For

People responsible for maintaining a Salesforce SaaS instance or developing changes for that Salesforce instance. Readers should have a basic understanding of the Salesforce platform and a desire to introduce a level of control around the changes being made, reduce issues on their Salesforce instance, and improve quality while increasing the throughput of changes they want to introduce into the platform.

About Lee Harding

Lee Harding, formerly a Senior Program Architect at Salesforce, is the Technology Director at Harwoods Group, a large automotive retail company in the United Kingdom. Harwoods are using Salesforce's technology at the heart of their digital transformation and considers it a key enabler for their business in the future. Over the past 35 years in IT, Lee has used his skills and experience to help large and small enterprises deliver their business transformations. Lee has handled big transformational programs, involving tens of thousands of users and has helped customers get the most out of their investment in the Salesforce Cloud technologies. Using his experience in large-scale transformation projects Lee has helped many businesses accelerate their implementations and see the benefits sooner, rather than later. Having a broad knowledge base and a keen interest in technology and its governance, Lee has been able to help customers navigate the pros and cons of technology decisions and keeps an open mind as to how technology can benefit his customers at the earliest opportunity, while instilling the right processes to help his customers be successful.

Lee Bayliss, a Senior Program Architect at Salesforce, has worked in the IT industry for over 25 years and has held various positions in operations, engineering, product design, technical leadership, and various lead architect positions for large service providers such as DXC (formerly, EDS/HPES). During Lee's extensive career in IT, he has worked across many industry sectors, including manufacturing, oil exploration, financial services, and health life sciences. Working with various enterprise businesses, Lee has amassed a wealth of experience delivering IT solutions ranging from lightweight projects to large scale business transformations. For the last 3 years, Lee has been working for Salesforce, a company which is diverse in nature, focused on customer success. Salesforce has created a huge ecosystem of products and services that can propel SME businesses to become trailblazers in their field. At Salesforce, Lee finds himself in a unique position providing guidance on all of the things that large (and small) organizations struggle with-how to implement the Salesforce platform and its components successfully, how to control all the moving parts, and how to drive value throughout the business in a world where digital transformation is a success imperative.

The content of this Chapter introduces the reader to the concepts of governance and how they need to construct their teams and processes to facilitate governance within their organisation. Additionally, the structure of our governance method is described, which sets the structure for the remainder of the book. The book is essentially split into two sections. The first section is the governance method, whilst the second section is the resources needed to perform the governance.

Resource Base

Key Points

Basic Structure

Adapting the SLPGM

Architecture Governance

Process Management

Scoping the Application Governance Cycle

Platform Team

CHAPTER 2: Application Architecture (Phase A)

Describes the method by which the application architecture is governed on the Salesforce platform. Areas covered are general architecture, localisation and global deployments, workflow and process, formulas and files and social.

Objectives

Approach

Inputs

Steps

Outputs

CHAPTER 3: Data Architecture (Phase B)

Describes the method by which the data architecture is governed. Areas covered are design and data optimization, performance, predictive and actual data volumes and data movement.

Objectives

Approach

Inputs

Steps

Outputs

CHAPTER 4: Identity & Access Management (Phase C)

This Chapter will focus on the governance of the identity and access management aspects of the application and Salesforce platform. These will form part of the technical standards and policies, but it is possible for an application to seek changes to these. For example, A Connected App (external to Salesforce) may be required that can only support a specific authentication solution, which is not part of the technical standards.

Objectives

Approach

Inputs

Steps

Outputs

CHAPTER 5: Sharing & Visibility (Phase D)

The Salesforce platform is very flexible and as such allows a developer to create applications with very little development experience. Obviously the more experience the developer, the more comprehensive the application can be. Salesforce has specifically focused on the ability to create applications and change configuration through clicks, negating in the majority of cases the need to actually write code. Creating applications and changing configuration via clicks is known as Declarative and the Salesforce platform has provided a significant amount of functionality and tailoring capability just through the declarative route. Declarative changes are stored in the metadata of the Org, and as such can be extracted (there are some limitations) and therefore analysed and governed. The approach to this phase is to describe how to take those declarative changes and assess them against the technical standards and policies.

Objectives

Approach

Inputs

Steps

Outputs

CHAPTER 6: Integration (Phase E)

Salesforce provides numerous solutions to integration and the right solution will very much depend upon what the requirements are that underpin the integration. However, fundamentally this phase is looking to compare the integration techniques that are part of the technical standards and policies with those that have been used. Then, determine those that have been used, have they been used correctly.

Objectives

Approach

Inputs

Steps

Outputs

CHAPTER 7: Apex, Visualforce & Lightning (Phase F)

On a shared platform, it is important that every developer takes maximum advantage of the platform to reduce the impact their application has on the overall platform. The phase focuses on governing the low-level platform capabilities delivered through Lightning, Visualforce and Apex.

Objectives

Approach

Inputs

Steps

Outputs

CHAPTER 8: Communities (Phase G)

This phase targets Community implementations specifically, which bring specific features into the Salesforce platform for consideration and governance. As Communities can target Customers, Employees and Partners it is important that any data held within the core Salesforce instance from which the Community is delivered is secured. Therefore, Communities brings about specific sharing capabilities and other considerations that should be reviewed.

Objectives

Approach

Inputs

Steps

Outputs

CHAPTER 9: Mobile Solutions (Phase H)

This phase targets the governance of deploying Salesforce to a mobile device. This will include the configuration and source code, any customization used and security implications.

Objectives

Approach

Inputs

Steps

Outputs

CHAPTER 10: Development Lifecycle & Deployment (Phase I)

The development lifecycle will be well defined in terms of the environments and tooling and the route to live that an application will take. The purpose of this phase is to have a means of governing this. In the main, this should not change regularly, but within the enterprise it is not unimaginable that additional Salesforce instances may arise, or that external parties are engaged. In these scenarios, the organization will want to determine whether these situations are adhering to the standards.

Objectives

Approach

Inputs

Steps

Outputs

CHAPTER 11: Resource Base

The Resource Base provides the reference material for all of the governance phases. This material is distilled to provide distinct references against which governance is simplified. Additionally, the Resource Base will form the basis for the documentation to support the development within the Salesforce platform. The purpose being, the reference material informs the developers on how to develop, as well as providing a reference to which governance can be performed. The subsequent Chapters within the Resource Base section have a consistent layout, which details the guidelines and best practices from Salesforce as well as a checklist to facilitate the governance process. In addition, any tooling that could be used to help accelerate the governance process is highlighted.

Overview

CHAPTER 12: Application Architecture (Phase A) Resource Base