Application Lifecycle Management consists of 8% of total score in Salesforce Platform Lifecycle and Deployment Architect Exam. The topic covers ALM, development methodologies, and governance strategies.
NOTE
Most of the content in this work was generated with the assistance of AI and carefully reviewed, edited, and curated by the author. If you have found any issues with the content on this page, please do not hesitate to contact me at support@issacc.com.
๐ Application Lifecycle Management (ALM) & Methodologies
๐ What is ALM?
- ALM = managing the entire life of an application โ from โ๏ธ design โ ๐ป development โ ๐งช testing โ ๐ release โ ๐ง maintenance.
- Provides a framework for bug fixes, enhancements, and smooth delivery.
- Stages:
1๏ธโฃ Plan Release
2๏ธโฃ Develop
3๏ธโฃ Test
4๏ธโฃ Build Release
5๏ธโฃ Test Release
6๏ธโฃ Release
โจ Benefits:
โ
Efficiency & productivity
โ
Avoids defects (quality assurance)
โ
Predictable & consistent releases
โ
Faster delivery
โ
Lower cost
โ
Long-term stability & maintenance
โ๏ธ Development Methodologies
๐ง Waterfall
- ๐ Linear steps โ each must finish before next.
- Good for: stable requirements, compliance-heavy projects, fixed deadlines.
- Pros: predictable cost/time, strong docs, structured process.
- Risks: โ inflexible, โ little feedback, โ slow to adapt, โ risk of dissatisfaction.
- Governance:
- ๐ Change Control Board (CCB)
- ๐ Milestone reviews
โก Agile
- ๐ Iterative, flexible approach (sprints = 2โ4 weeks).
- Requirements evolve โ continuous delivery & stakeholder input.
- Pros: adaptability, collaboration, early value delivery.
- Risks: โ ๏ธ scope creep, โ ๏ธ quality trade-offs, โ ๏ธ integration challenges, โ ๏ธ weak docs.
- Governance:
- ๐ Backlog prioritization
- ๐ฃ Daily stand-ups
- ๐ Sprint reviews & retrospectives
๐ Scrum (Agile framework)
- Core values: ๐ช Commitment, ๐ฆ Courage, ๐ฏ Focus, ๐ Openness, ๐ Respect
- Roles: Product Owner, Scrum Master, Dev Team
- Meetings: planning, daily stand-ups, reviews, retrospectives
- Artifacts: backlog, sprint backlog, burndown chart, increments
๐ Lean (Agile framework)
- โ๏ธ Eliminate waste, โป๏ธ continuous improvement, ๐ efficiency + quality
- Principles: Identify value โ Map value stream โ Create flow โ Establish pull โ Seek perfection
๐ Kanban (Agile framework)
- ๐ Visual board โ cards flow left โ right
- ๐ข WIP limits โ avoid overload
- โฑ Metrics: cycle time & throughput
- Flexible โ embraces small, incremental changes
๐ Hybrid
- ๐งฉ Mix of Waterfall (structure, upfront docs) + Agile (flexibility, feedback)
- Good for: complex integrations, mid-sized companies balancing old & new.
- Risks: โ ๏ธ confusing rules, โ ๏ธ high overhead, โ ๏ธ resource strain.
- Mitigation: ๐ training, ๐ข clear scope, โณ phase-gate reviews
๐ก Governance Strategies
Governance = structure to control changes, align priorities, ensure security/compliance.
- Waterfall: CCB + Milestone reviews
- Agile: backlog priority, daily stand-ups, sprint ceremonies
- Benefits: โ efficiency, โ transparency, โ compliance, โ resource optimization
๐ข Case Scenarios & Solutions
1๏ธโฃ Enterprise Client (regulated)
- Needs: stable scope, fixed deadline, compliance docs.
- โ Solution: Waterfall (structured, documentation-heavy).
- โ ๏ธ Risks: late change inflexibility โ mitigate with strong upfront requirements + milestone reviews.
2๏ธโฃ E-Commerce Startup (fast-paced)
- Needs: evolving requirements, frequent updates, flexibility.
- โ Solution: Agile (iterative, incremental delivery, user feedback).
- โ ๏ธ Risks: scope creep & weak planning โ mitigate with backlog prioritization + sprint discipline.
3๏ธโฃ Retail Company (mid-sized)
- Needs: integration + customization, balance of structure & adaptability.
- โ Solution: Hybrid (Waterfall for integration + Agile for custom features).
- โ ๏ธ Risks: confusion & resource strain โ mitigate with training, clear rules, phase-gate reviews.
4๏ธโฃ Healthcare Provider (values-driven)
- Needs: patient-first culture, respect, openness; new to Agile but curious.
- โ Solution: Scrum (values align perfectly).
- โ ๏ธ Risks: new to iteration & transparency โ mitigate with training, team-building, focus on sprint goals.
๐ Development Methodologies Cheat Sheet
๐ Methodology | ๐ Pros | โ ๏ธ Risks | ๐ก Governance | ๐ฏ Best Fit |
---|---|---|---|---|
๐ง Waterfall | โ
Clear structure โ Strong docs โ Predictable | โ No flexibility โ Low feedback โ Risk of mismatch | ๐ Change Control Board ๐ Milestone reviews | ๐ข Regulated industries ๐ Fixed scope & deadline |
โก Agile | ๐ Iterative ๐ค Collab focus ๐ Fast delivery | โ ๏ธ Scope creep โ ๏ธ Weak docs โ ๏ธ Quality trade-offs | ๐ Backlog priority<br๐ฃ Daily stand-ups ๐ Sprint reviews | ๐ Startups ๐ Rapid change ๐ฌ Frequent feedback |
๐ Scrum | โฑ 2โ4 wk sprints ๐งโ๐คโ๐ง Clear roles ๐ก Values-driven (Commitment, Courage, Focus, Openness, Respect) | โ Needs full engagement โ Culture resistance โ Focus drift | ๐ Sprint ceremonies ๐ Backlogs & charts ๐ Retrospectives | โค๏ธ Value-driven orgs ๐ฅ Healthcare / team focus ๐ Iterative projects |
๐ Lean | โ๏ธ Cut waste ๐ Efficient use โป๏ธ Continuous improve | โ ๏ธ Risk of under-planning โ ๏ธ Slow decisions | ๐บ Value mapping ๐ Learning loops | ๐ญ Efficiency seekers ๐ก Process improvement |
๐ Kanban | ๐ Visual board ๐ข WIP limits ๐ Metrics (cycle/throughput) | โ Bottlenecks โ Less structure | ๐ Track metrics ๐งฎ WIP discipline | ๐ง Ops/support teams ๐ Incremental change |
๐ Hybrid | ๐งฉ Structured + Flexible ๐ก Early risk detect ๐ Iterative feedback | โ ๏ธ Confusion risk โ ๏ธ High overhead โ ๏ธ Diluted benefits | ๐ Training ๐ข Clear rules โณ Phase-gates | ๐ Mid-size orgs ๐ Complex integrations โ๏ธ Balance need |
๐ฏ Key Takeaways
- ๐ง Waterfall = ๐ Stability + Compliance-heavy projects
- โก Agile = ๐ Speed + Flexibility + Frequent feedback
- ๐ Hybrid = โ๏ธ Balance + Complex integrations
- ๐ Scrum = โค๏ธ Values-driven teams
- ๐ Lean = โ๏ธ Efficiency + Waste reduction
- ๐ Kanban = ๐ Flow + Incremental improvements
๐ Flow Charts
flowchart TD A([๐ Start: Pick Methodology]) --> B{๐งญ Stable Requirements?} B -- Yes --> C{๐งพ Heavy Compliance?} C -- Yes --> W[๐ง WATERFALL<br/>Structured, docs, predictable] C -- No --> D{๐งฉ Complex Integrations?} D -- Yes --> H[๐ HYBRID<br/>Plan upfront + iterate features] D -- No --> W B -- No --> E{โก Need Speed & Flexibility?} E -- Yes --> F{๐งโ๐คโ๐ง Stakeholders Available?} F -- Yes --> G{โค๏ธ Culture fits Scrum values?} G -- Yes --> S[๐ SCRUM<br/>2โ4wk sprints, roles, ceremonies] G -- No --> I{๐ง Work Type?} I -- Flow/Support --> K[๐ KANBAN<br/>Visual WIP, continuous flow] I -- Project/Features --> AGL[โก AGILE<br/>Iterative delivery, evolving scope] F -- No --> K E -- No --> D %% Efficiency path A --> L{โ๏ธ Focus on Efficiency?} L -- Yes --> LEAN[๐ LEAN<br/>Waste cut, value stream, Kaizen] L -- No --> B
๐ Flashcards
What is ALM and what are its stages?
- ALM = manage an appโs life from design to release and ongoing fixes/enhancements
- Stages: Plan Release โ Develop โ Test โ Build Release โ Test Release โ Release
Why use ALM? (top benefits)
- Avoids defects โข Increases efficiency โข Improves consistency โข Faster delivery โข Reduces cost โข Supports maintenance & long-term stability
What is a development methodology (in Salesforce context)?
- A structured set of practices across planning, design, development, testing, deployment, maintenance/support, and governance
Name the main methodologies and agile frameworks covered
- Methodologies: Waterfall, Agile, Hybrid
- Frameworks: Scrum, Lean, Kanban
Waterfall: when and why?
- Stable, well-defined requirements โข Compliance/docs heavy โข Fixed deadline โข Stakeholder touchpoints at milestones โข Time/cost set early
Waterfall: key risks
- Inflexible to late change โข Minimal feedback โข Hard to accommodate new risks โข Heavy docs may not add value โข Risk of customer dissatisfaction
Agile: when and why?
- Evolving requirements โข Iterative planning/execution โข Incremental delivery โข Continuous stakeholder engagement โข Time/cost refined over time
Agile: key risks
- Scope creep โข Excessive customer input derails focus โข Quality can suffer with speed โข Underestimation without upfront planning โข Thin documentation โข Integration challenges across teams
Hybrid: what is it?
- Combines Waterfall structure (upfront planning, milestones, early risk assessment) with Agile flexibility (iterative cycles, feedback)
Hybrid: key risks
- Confusion on when to use which โข Cultural conflicts โข Higher overhead โข Resource strain โข Diluted benefits if poorly balanced
Scrum: core mechanics (quick recap)
- Incremental delivery in 2โ4 week sprints โข Roles: Product Owner, Scrum Master, Dev Team โข Ceremonies: planning, daily, review, retro โข Artifacts: product backlog, sprint backlog, burndown, increment
Scrum: five values
- Commitment โข Courage โข Focus โข Openness โข Respect
Lean: principles (software lens)
- Eliminate waste โข Build quality in โข Continuous learning/Kaizen โข Efficient use of resources โข Just-in-time decisions โข Identify value โ Map value stream โ Create flow โ Establish pull โ Seek perfection
Kanban: traits & metrics
- Visualize workflow on board โข Limit WIP per stage โข Embrace small, evolutionary change โข Metrics: cycle time, throughput
Define governance in this context
- Structure to handle and track changes effectively so programs deliver outcomes on time/quality; aligns business and IT
Governance focus and benefits
- Focus: release mgmt, change request prioritization/approval, schedule, communication
- Benefits: efficiency, security/compliance, better resource use, collaboration, transparency
Waterfall governance strategies
- Change Control Board (CCB) to assess/approve scope changes โข Regular milestone reviews for progress, timeline, budget, compliance
Agile governance practices
- Product owner backlog prioritization โข Daily stand-ups โข Sprint reviews โข Retrospectives (continuous improvement and transparency)
๐งญ Scenario Cards
Scenario 1: US enterprise, stable scope, heavy compliance, fixed deadline, legacy integrations โ what to choose and why?
- Choose Waterfall: linear/structured path, strong documentation for compliance, predictable timelines; mitigate change inflexibility via exhaustive requirements + early feasibility/architecture + milestone reviews
Scenario 2: UK startup, fast-changing needs, frequent updates, real-time feedback โ what to choose and why?
- Choose Agile: iterative, frequent reassessment, small increments, close collaboration; mitigate risks via robust backlog prioritization, controlled scope changes, scheduled demos, disciplined sprint planning
Scenario 3: AU mid-sized retail, complex integrations, wants structure + flexibility โ what to choose and why?
- Choose Hybrid: Waterfall for integration planning/milestones + Agile sprints for custom features and feedback; mitigate confusion with clear method boundaries, team training, resource planning, and phase-gate reviews
Scenario 4: JP healthcare provider, patient-first culture, values openness/respect, new to Agile โ what framework and risks?
- Pick Scrum (values align: Commitment, Courage, Focus, Openness, Respect)
- Risks & mitigations: sustain engagement in ceremonies (coaching & support) โข Resistance to unfamiliar practices (change mgmt, training) โข Operational distractions (protect sprint focus) โข Transparency discomfort (feedback training) โข Potential conflicts (team-building)
๐งช Quick Check Mixers
Match each: Waterfall โข Agile โข Hybrid โ best-fit shorthand
- Waterfall = Stability + Compliance + Fixed deadlines
- Agile = Flexibility + Iteration + Stakeholder feedback
- Hybrid = Structured plan + Adaptive delivery
One-liners: how do Scrum/Lean/Kanban complement Agile?
- Scrum = roles/ceremonies/artifacts for iterative cadence โข Lean = value + efficiency + waste cut โข Kanban = visual flow + WIP control + flow metrics