When is the best time to release a product or Solution to the marketplace?

Question

Options

• AAt the end of the IP Iteration.
• BAt each PI boundary, provided there are no PI defects.
• CWhenever it meets relevant governance and market criteria.
• DAt quarterly boundaries.

• A
  3% (1)
• B
  9% (3)
• C
  74% (26)
• D
  14% (5)

Explanation

Releasing whenever it meets relevant governance and market criteria (C) is correct because product release decisions should be driven by business readiness, regulatory compliance, and market opportunity - not by artificial calendar boundaries. Agile frameworks like SAFe explicitly decouple deployment from release, meaning working software can be ready well before or after any iteration or PI boundary.

Why the distractors fail:

• A (end of IP Iteration) is wrong - the Innovation and Planning iteration is for planning, innovation, and hardening, not a mandatory release gate.
• B (PI boundary, no PI defects) is wrong - waiting for PI boundaries introduces unnecessary delay and "zero defects" is an unrealistic bar that conflates quality gates with release timing.
• D (quarterly boundaries) is wrong - this is an arbitrary time-box with no connection to business or market readiness.

Memory tip: Think "release on readiness, not on the calendar." If the product is safe, compliant, and the market is right - ship it. SAFe's principle of releasing on demand means the business, not the sprint clock, pulls the trigger.

No community discussion yet for this question.