Customer Discovery - Implementation Lifecycle

Question 1

Implementation Lifecycle Phases

Answer 1

Analyze, Build, Deliver, Operate

Question 2

Rapid Application Development

Answer 2

Application development model focused on Speed, User Strategy, and Prototyping

Question 3

Application Lifecycle Management

Answer 3

3 development models:
change set
org development
package development

Question 4

Analyze phase

Answer 4

gather requirements
org impact analysis
process mapping
formulate user stories

Question 5

build phase

Answer 5

configuration
development
org documentation
testing
building release
testing release

Question 6

deliver phase

Answer 6

securing backup
deployment
data imports
actual release

Question 7

operate phase

Answer 7

monitor
feedback
support
restoring data
compliance

Question 8

Application Lifecycle Management Steps

Answer 8

1. Plan Release
2. Develop
3. Test
4. Build Release
5. Test Release
6. Release

Question 9

release management categories

Answer 9

patch bugs and simple changes
- reports, dashboards, list views, email templates

minor changes with limited impact
- changes in automation, change management and thorough testing not required

major changes with significant impact
- changes with one or more dependencies. Requires thorough testing and organized change management

Question 10

Rapid Application Development info

Answer 10

developers work directly with focus groups
method is opposite of linear waterfall method
no-code and low code solutions to reduce development time

Question 11

Change Sets

Answer 11

Manage app using declarative toold

Question 12

ORG Development

Answer 12

Salesforce CLI is used to extract metadata from development env. and integrate with version control system

Question 13

Package Development

Answer 13

Different customizations managed as separate packages. Source of truth in metadata.

Question 14

Release type - Patch bug fixes and simple changes

Answer 14

reports, dashboards, list views, email templates

Question 15

release type - minor changes with limited impact

Answer 15

new trigger impacting a single business process. Requires a little testing but no training

Question 16

release type - major changes with significant impact

Answer 16

changes with one or more dependencies
testing, training

Question 17

change set development

Answer 17

change and update metadata
what gets released is only metadata that has changed

change set is the set of metadata to be changed

must track changes that are not available in the metadata AI. Will have to manually change them

change sets can ADD but can’t delete fields

using change sets, can accidentally overwrite someone else’s change set.

Question 18

org development model

Answer 18

use the salesforce CLI (command line interface) to extract metadata from development environment to integrate with a version control system

using a VCS, customization conflicts can be tracked

can make CLI script to automate tasks

Question 19

package development model

Answer 19

manage different customizations as different packages, can be on own release schedule, not as one big release to changes in the org

each package includes all of the metadata - changed AND unchanged relevant components

SOURCE OF TRUTH IN THE METADATA

separate release schedules for each package

Question 20

change set development source of truth

Answer 20

metadata already in the environment and last build of change set. On its own, a change set doesn’t present the complete picture because it contains only what’s changed.

Question 21

Scratch orgs

Answer 21

Package development - empty orgs (no metadata or data) that are easy to create and dispose of as needed

You can configure scratch orgs to be different Salesforce editions with different features and preferences. What’s more, you can re-use and share the scratch org definition file with other team members, because it’s part of the project integrated into the VCS

Question 22

how to use scratch orgs for development?

Answer 22

first push the source from your project in the VCS to sync the scratch org with the same metadata.

Question 23

what is package dependency?

Answer 23

A metadata component can be in only one package at a time.

If more than one package needs the same component, you can devise a modular package strategy for that component.

A package containing one or more metadata components shared by multiple packages is a package dependency.

Question 24

When using the package development model, which metadata changes do you need to track manually?

Answer 24

changes to components not yet supported by source tracking

Question 25

key benefit of scratch org

Answer 25

you can share its definition file with others

Question 26

what is safe to change in a production org?

Answer 26

customizations that don’t affect data (dashboards, reports, email templates)

Question 27

Can you write apex code in a production org?

Answer 27

No, only development

Question 28

what is application lifecycle management?

Answer 28

defines steps of managing app development process.

Also defines steps for application updating process (bug fixes, new features)

Question 29

what is salesforce CLI

Answer 29

used in org development process

Command line interface - useful to:
extract metadata from a development environment to integrate with a version control system (VCS)

script routine tasks and boost the productivity

Question 30

when to move from change sets development to package development model?

Answer 30

When releases become so complex that it makes sense to manage the org as multiple containers

Question 31

what is a package version, and what does it allow you to do?

Answer 31

A package version is a fixed snapshot of the package contents and related metadata.

The package version lets you manage what’s different each time you release or deploy a specific set of changes added to a package.

If you’re introducing metadata changes to an already deployed package, you upgrade from the current package version to the newer package version.