Development Lifecycle & Deployment

Key Takeaways

Development Lifecycle covers environment strategy, CI/CD pipelines, testing, governance, and risk management. Understand sandbox types and scratch orgs, know when to use change sets vs unlocked packages vs CLI deployments, and design a test pyramid with clear UAT criteria. Governance (ARB, CAB, RACI) and risk mitigation are frequent review board topics.

This domain covers project management, testing strategies, governance, environment management, and release management.

Objectives

• Project risk identification and mitigation strategies
• Technical considerations given customer project environment and development methodology
• Recommend comprehensive test strategy
• Governance considerations, stakeholders, and impact of decisions
• Platform tools for environment management
• Source control and continuous integration for release management

Study Content

Core Topics

• Environment Strategy — Sandbox types, scratch orgs, DevHub, refresh planning, data masking, post-copy scripts
• CI/CD & Deployment — Git branching, Salesforce DX CLI, change sets, unlocked packages, CI/CD tools, deployment strategies, feature flags
• Testing Strategy — Test pyramid, Apex unit testing, integration testing, UAT planning, performance testing, automation tools
• Governance Model — ARB, CAB, RACI matrix, Salesforce CoE model, ADRs, compliance (GDPR, HIPAA, SOX), data governance
• Risk Management — Risk categories, probability x impact matrix, risk register, common CTA scenario risks, mitigation strategies

Decision Guides & Analysis

• Decision Guides — Mermaid decision flowcharts for branching strategy, CI/CD tool selection, sandbox strategy, testing approach
• Best Practices — DevOps best practices, anti-patterns, and maturity assessment
• Trade-offs — Agile vs waterfall, change sets vs CLI, full vs partial sandbox, manual vs automated testing, centralized vs federated CoE, release cycle length

Practice

• Domain Grilling: D6 Development Lifecycle Q&A

Related Topics

Development lifecycle decisions depend on what is being built and delivered:

• Solution Architecture — The chosen solution architecture determines the complexity of the deployment pipeline
• Integration — CI/CD pipelines must handle integration deployments, connected app configs, and API versioning
• Communication — Release planning, stakeholder reporting, and change communication are lifecycle deliverables

Frequently Asked Questions

What development lifecycle topics does the CTA exam test?

The CTA exam covers environment strategy (sandbox types, scratch orgs, DevHub), CI/CD pipelines (Salesforce DX CLI, unlocked packages, deployment strategies), testing strategy (test pyramid, Apex testing, UAT, performance testing), governance models (ARB, CAB, RACI, CoE), and risk management (risk registers, probability x impact matrices, mitigation strategies).

How is Development Lifecycle scored in the CTA review board?

Judges evaluate whether your environment strategy matches the project complexity, whether your CI/CD approach is realistic for the team and timeline, whether your testing strategy covers all levels of the test pyramid, whether governance structures are appropriate for the organization size, and whether you have identified and addressed the key project risks with concrete mitigation plans.

What are the most common mistakes in Development Lifecycle during the CTA exam?

Candidates commonly fail by proposing an overly complex CI/CD pipeline for a small team, not addressing data migration testing with trial loads, ignoring governance for multi-team environments, using change sets when the scenario complexity clearly warrants source-driven development, and failing to identify risk factors that are explicitly mentioned in the scenario paper.

How should I choose between change sets, Salesforce CLI, and unlocked packages?

Use change sets only for small organizations with simple, infrequent deployments. Use Salesforce CLI (source tracking, scratch orgs) for teams practicing source-driven development with version control. Use unlocked packages when you need modular, versioned deployments with dependency management across multiple teams. The scenario’s team size, release frequency, and organizational complexity determine the right choice.

What governance structures should I include in my CTA solution?

At minimum, address an Architecture Review Board (ARB) for design decisions, a Change Advisory Board (CAB) for production deployments, a RACI matrix for key project roles, and a Center of Excellence (CoE) model for ongoing Salesforce governance. Scale the formality to the organization — a 50-person company needs lighter governance than a 10,000-person enterprise.