4.5.10: Scenario 9 – Budget Threshold Breach and CFO Escalation
- Page ID
- 54815
\( \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 9 – Budget Threshold Breach and CFO Escalation
Scenario Context
Project Reckon is in final stabilization for Release Candidate 1 (RC1).
Across recent iterations:
-
Integration defects have been reduced
-
QA effort remains elevated
-
Schedule is slightly behind but within tolerance
However, the cumulative financial trajectory has shifted.
Sustained increases in QA effort and extended stabilization activities have now pushed total project cost beyond the acceptable variance threshold.
This has triggered attention from Finance leadership.
Email from Julie Rama
Subject: RC1 Status – Final Stabilization and Resource Alignment
Hi,
We are nearing final RC1 readiness and continue to focus on ensuring integration stability and QA completeness.
Current status:
-
Velocity: 93% of baseline
-
Defects: 10 open (all medium and low severity)
-
Burn rate: +7.8% cumulative
-
Schedule: ~5 days behind (within tolerance)
The elevated burn rate is primarily due to:
-
Increased QA effort for integration validation
-
Extended regression cycles to ensure stability
At this stage, we believe reducing QA effort could introduce unnecessary risk to RC1 quality.
We recommend maintaining current staffing levels through RC1 completion.
Please let me know if you would like to discuss further.
Best,
Julie
Internal Email from CFO
Subject: Reckon Budget Status
Hi,
I’ve reviewed the latest cost reports for Project Reckon.
It appears that we are now exceeding our agreed budget tolerance.
I understand that some variance may be expected, but I need clarity on:
-
Why cost is trending above plan
-
Whether this variance is temporary or structural
-
What actions are being taken to bring the project back within control
We need to ensure that this project does not establish a pattern of cost overruns.
Please provide a clear assessment and plan of action.
Thanks,
[CFO Name]
Attachment A – Budget Status Summary
| Category | Planned | Actual | Variance |
|---|---|---|---|
| Development | On track | Slight variance | +1.5% |
| QA | Elevated | Significant increase | +18% |
| Total Project Cost | — | +7.8% cumulative | Above tolerance |
Attachment B – Cost Trend
-
Iteration 2: +2.8%
-
Iteration 3: +4.2%
-
Iteration 4: +6.4%
-
Current: +7.8%
Trend: Consistent upward trajectory.
Student Assignment
You are the Project Manager at C-Bay.
The project is technically stabilizing.
However, financial control has now been breached.
You must address:
-
CFO concerns regarding cost discipline
-
Vendor recommendation to maintain elevated QA effort
-
Whether to prioritize cost control or delivery stability
-
How to bring the project back within acceptable financial bounds
Prepare a formal written response.
Required Submission Structure
Your memorandum must include:
1️⃣ Executive Position
-
Is the project still under control?
-
Is the budget variance acceptable?
-
Is CFO concern justified?
2️⃣ Budget Analysis
-
Is the +7.8% variance structural or temporary?
-
Is increased QA effort justified?
-
Should corrective financial action be taken?
3️⃣ Cost Control Strategy
-
Should QA effort be reduced?
-
Should cost be absorbed to protect quality?
-
Should alternative cost mitigation strategies be applied?
4️⃣ Vendor Management Position
-
Should ZynoxDev adjust staffing levels?
-
Should cost accountability be enforced more strictly?
-
Should financial transparency be increased?
5️⃣ Executive Communication Strategy
-
How will you respond to the CFO?
-
How will you explain cost vs quality trade-offs?
-
How will you demonstrate control?
6️⃣ Risk Assessment
Identify and evaluate:
-
Budget overrun risk
-
Quality risk (if cost reduced)
-
Delivery risk
-
Vendor dependency risk
Assign likelihood and impact.
7️⃣ Directive to ZynoxDev
Provide a clear directive, such as:
-
Maintain QA effort with financial justification
-
Optimize QA allocation without reducing coverage
-
Provide detailed cost breakdown and forecast
-
Identify areas for cost recovery
-
Align staffing to bring burn rate under control
Your directive must balance:
-
Financial discipline
-
Delivery quality
-
Vendor relationship
Learning Focus
Scenario 9 introduces:
-
Financial accountability under executive scrutiny
-
Balancing cost vs quality trade-offs
-
Managing CFO-level communication
-
Identifying structural vs temporary cost issues
-
Enforcing vendor cost discipline
Students must demonstrate:
-
Financial maturity
-
Strategic prioritization
-
Executive communication clarity
-
Structured corrective thinking
This scenario shifts the core question from:
“Are we delivering the product?”
to:
“Are we delivering the product responsibly?”

