Which process guides the final approval for a release in SAFe?

Question

Options

• ARelease Governance
• BLean Portfolio Management
• CProduct Management
• DContinuous Delivery Pipeline

• A
  5% (2)
• B
  3% (1)
• C
  90% (36)
• D
  3% (1)

Explanation

Product Management owns the release approval process in SAFe because they hold accountability for defining what gets released, when, and to whom - making the final call on whether a release meets the intended business value and readiness criteria.

Why the distractors are wrong:

• A. Release Governance - Not a defined SAFe role or process; governance in SAFe is handled through existing roles, not a separate governance body for releases.
• B. Lean Portfolio Management (LPM) - LPM operates at the portfolio level, focused on strategy, funding, and Epics - not the tactical approval of individual releases.
• D. Continuous Delivery Pipeline - This is a technical capability/set of practices (Continuous Exploration, Integration, Deployment, Release on Demand), not a decision-making authority.

Memory tip: Think of Product Management as the "business owner of the release" - they bridge customer needs and delivery teams, so it makes sense they hold the final release approval key. If you see a question about who decides on a release, think Product Management = release authority.

No community discussion yet for this question.