Skip to main content
Workforce LibreTexts

4.5.11: Scenario 10 – Release Candidate Go / No-Go Decision

  1. Last updated
  2. Save as PDF
  • Page ID
    54816

    • \( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)

    \( \newcommand{\dsum}{\displaystyle\sum\limits} \)

    \( \newcommand{\dint}{\displaystyle\int\limits} \)

    \( \newcommand{\dlim}{\displaystyle\lim\limits} \)

    \( \newcommand{\id}{\mathrm{id}}\) \( \newcommand{\Span}{\mathrm{span}}\)

    ( \newcommand{\kernel}{\mathrm{null}\,}\) \( \newcommand{\range}{\mathrm{range}\,}\)

    \( \newcommand{\RealPart}{\mathrm{Re}}\) \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)

    \( \newcommand{\Argument}{\mathrm{Arg}}\) \( \newcommand{\norm}[1]{\| #1 \|}\)

    \( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)

    \( \newcommand{\Span}{\mathrm{span}}\)

    \( \newcommand{\id}{\mathrm{id}}\)

    \( \newcommand{\Span}{\mathrm{span}}\)

    \( \newcommand{\kernel}{\mathrm{null}\,}\)

    \( \newcommand{\range}{\mathrm{range}\,}\)

    \( \newcommand{\RealPart}{\mathrm{Re}}\)

    \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)

    \( \newcommand{\Argument}{\mathrm{Arg}}\)

    \( \newcommand{\norm}[1]{\| #1 \|}\)

    \( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)

    \( \newcommand{\Span}{\mathrm{span}}\) \( \newcommand{\AA}{\unicode[.8,0]{x212B}}\)

    \( \newcommand{\vectorA}[1]{\vec{#1}}      % arrow\)

    \( \newcommand{\vectorAt}[1]{\vec{\text{#1}}}      % arrow\)

    \( \newcommand{\vectorB}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \( \newcommand{\vectorC}[1]{\textbf{#1}} \)

    \( \newcommand{\vectorD}[1]{\overrightarrow{#1}} \)

    \( \newcommand{\vectorDt}[1]{\overrightarrow{\text{#1}}} \)

    \( \newcommand{\vectE}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash{\mathbf {#1}}}} \)

    \( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \(\newcommand{\longvect}{\overrightarrow}\)

    \( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)

    \(\newcommand{\avec}{\mathbf a}\) \(\newcommand{\bvec}{\mathbf b}\) \(\newcommand{\cvec}{\mathbf c}\) \(\newcommand{\dvec}{\mathbf d}\) \(\newcommand{\dtil}{\widetilde{\mathbf d}}\) \(\newcommand{\evec}{\mathbf e}\) \(\newcommand{\fvec}{\mathbf f}\) \(\newcommand{\nvec}{\mathbf n}\) \(\newcommand{\pvec}{\mathbf p}\) \(\newcommand{\qvec}{\mathbf q}\) \(\newcommand{\svec}{\mathbf s}\) \(\newcommand{\tvec}{\mathbf t}\) \(\newcommand{\uvec}{\mathbf u}\) \(\newcommand{\vvec}{\mathbf v}\) \(\newcommand{\wvec}{\mathbf w}\) \(\newcommand{\xvec}{\mathbf x}\) \(\newcommand{\yvec}{\mathbf y}\) \(\newcommand{\zvec}{\mathbf z}\) \(\newcommand{\rvec}{\mathbf r}\) \(\newcommand{\mvec}{\mathbf m}\) \(\newcommand{\zerovec}{\mathbf 0}\) \(\newcommand{\onevec}{\mathbf 1}\) \(\newcommand{\real}{\mathbb R}\) \(\newcommand{\twovec}[2]{\left[\begin{array}{r}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\ctwovec}[2]{\left[\begin{array}{c}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\threevec}[3]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\cthreevec}[3]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\fourvec}[4]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\cfourvec}[4]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\fivevec}[5]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\cfivevec}[5]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\mattwo}[4]{\left[\begin{array}{rr}#1 \amp #2 \\ #3 \amp #4 \\ \end{array}\right]}\) \(\newcommand{\laspan}[1]{\text{Span}\{#1\}}\) \(\newcommand{\bcal}{\cal B}\) \(\newcommand{\ccal}{\cal C}\) \(\newcommand{\scal}{\cal S}\) \(\newcommand{\wcal}{\cal W}\) \(\newcommand{\ecal}{\cal E}\) \(\newcommand{\coords}[2]{\left\{#1\right\}_{#2}}\) \(\newcommand{\gray}[1]{\color{gray}{#1}}\) \(\newcommand{\lgray}[1]{\color{lightgray}{#1}}\) \(\newcommand{\rank}{\operatorname{rank}}\) \(\newcommand{\row}{\text{Row}}\) \(\newcommand{\col}{\text{Col}}\) \(\renewcommand{\row}{\text{Row}}\) \(\newcommand{\nul}{\text{Nul}}\) \(\newcommand{\var}{\text{Var}}\) \(\newcommand{\corr}{\text{corr}}\) \(\newcommand{\len}[1]{\left|#1\right|}\) \(\newcommand{\bbar}{\overline{\bvec}}\) \(\newcommand{\bhat}{\widehat{\bvec}}\) \(\newcommand{\bperp}{\bvec^\perp}\) \(\newcommand{\xhat}{\widehat{\xvec}}\) \(\newcommand{\vhat}{\widehat{\vvec}}\) \(\newcommand{\uhat}{\widehat{\uvec}}\) \(\newcommand{\what}{\widehat{\wvec}}\) \(\newcommand{\Sighat}{\widehat{\Sigma}}\) \(\newcommand{\lt}{<}\) \(\newcommand{\gt}{>}\) \(\newcommand{\amp}{&}\) \(\definecolor{fillinmathshade}{gray}{0.9}\)

    Scenario 10 – Release Candidate Go / No-Go Decision

    Scenario Context

    Project Reckon has completed final stabilization activities for Release Candidate 1 (RC1).

    Over the past several iterations:

    • Integration defects have been reduced significantly

    • QA coverage has increased

    • Velocity has remained slightly below baseline

    • Budget has exceeded acceptable variance thresholds

    • Schedule has slipped slightly but remains within tolerance

    The product is now functionally complete and ready for decision.

    The question is no longer:

    “Can we build Reckon?”

    The question is:

    “Should we release RC1 now?”

    Email from Julie Rama

    Subject: RC1 Readiness – Go / No-Go Decision Required

    Hi,

    We have completed final stabilization and are ready to proceed with RC1.

    Here is the current status:

    1. Product Readiness

    • All core features implemented

    • Reporting module stable (project-level functionality only)

    • Integration with iPET functioning under tested scenarios

    • No show-stopper defects

    2. Defect Status

    • 8 open defects (all low severity)

    • No high or medium severity issues remaining

    • Known minor UI inconsistencies and edge-case sync delays

    3. Performance Summary

    • Velocity: 93% of baseline

    • QA coverage: Increased significantly

    • Integration stability: Acceptable under tested conditions

    4. Budget & Schedule

    • Budget: +8.2% cumulative (above tolerance)

    • Schedule: ~6 days behind original plan (within tolerance)

    5. Recommendation

    From our perspective, RC1 is ready for release.

    Remaining issues are minor and can be addressed in subsequent iterations.

    Delaying release would allow for:

    • Additional QA refinement

    • Resolution of minor defects

    • Slight improvement in performance consistency

    However, this would also:

    • Extend schedule

    • Increase cost

    • Delay stakeholder visibility

    Please confirm whether you would like to proceed with RC1 release or extend stabilization.

    Best,
    Julie

    Attachment A – Final Status Snapshot

    Category Status
    Features Complete
    Integration Stable (tested scenarios)
    Defects 8 low severity
    Budget +8.2%
    Schedule Within tolerance

    Attachment B – Remaining Defect Summary

    • UI alignment inconsistencies

    • Minor reporting latency under edge cases

    • Non-blocking sync timing delays

    Student Assignment

    You are the Project Manager at C-Bay.

    You must now make a Go / No-Go decision for RC1.

    There is no perfect answer.

    You must evaluate:

    • Product readiness

    • Risk exposure

    • Budget overrun

    • Schedule implications

    • Stakeholder expectations

    Prepare a formal written response to Julie Rama.

    Required Submission Structure

    Your memorandum must include:

    1️⃣ Executive Decision

    Clearly state:

    • Go (proceed with RC1 release)
      or

    • No-Go (delay release)

    This must be unambiguous.

    2️⃣ Decision Justification

    Explain your reasoning across:

    • Product quality

    • Defect acceptability

    • Integration stability

    • Budget considerations

    • Schedule impact

    3️⃣ Risk Acceptance Statement

    Identify:

    • What risks are being accepted

    • Why they are acceptable (or not)

    • What mitigation will follow post-release

    4️⃣ Financial Position

    • Is budget overrun acceptable at this stage?

    • Does further delay worsen financial position?

    • How does cost influence your decision?

    5️⃣ Stakeholder Impact

    • How will this decision affect executive confidence?

    • How will it impact future development phases?

    • What message will be communicated to leadership?

    6️⃣ Directive to ZynoxDev

    Provide clear instruction, such as:

    • Proceed with RC1 release immediately

    • Delay release and address specific defects

    • Focus additional QA on defined areas

    • Prepare post-release remediation plan

    Learning Focus

    Scenario 10 introduces:

    • Decision-making under imperfect conditions

    • Risk acceptance vs risk avoidance

    • Cost vs quality trade-offs

    • Release readiness judgment

    • Executive accountability

    Students must demonstrate:

    • Confidence in decision-making

    • Structured reasoning

    • Acceptance of trade-offs

    • Ownership of outcome

    Final Reflection Requirement

    Following submission, students must complete:

    Reflection Questions:

    1. What risks did you accept in your decision?

    2. What risks did you choose to avoid?

    3. How did budget influence your judgment?

    4. Would you make the same decision in a real enterprise setting? Why or why not?

    Capstone Insight

    This scenario reinforces:

    There is no “perfect release.”

    Only:

    • Managed risk

    • Informed judgment

    • Accountable decision-making

    4.5.11: Scenario 10 – Release Candidate Go / No-Go Decision is shared under a CC BY 4.0 license and was authored, remixed, and/or curated by LibreTexts.