4.5.15: Scenario 14 – Resource Expansion and Quality Instability
- Page ID
- 54820
\( \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 14 – Resource Expansion and Quality Instability
Scenario Context
Following capacity constraints identified in the previous scenario, a decision was made to increase ZynoxDev’s development and QA resources to accelerate delivery of prioritized enhancements.
New team members have been onboarded over the past iteration.
Initial expectations were:
-
Increased development velocity
-
Faster backlog throughput
-
Improved responsiveness to enhancement requests
However, early indicators now show unexpected side effects.
Email from Julie Rama
Subject: Iteration Update – Resource Expansion Impact
Hi,
I wanted to provide an update following the recent addition of new development and QA resources.
1. Current Performance
-
Velocity: 88% of baseline (slight decrease from previous iteration)
-
Defects: 26 open (increase from prior iteration)
-
3 high severity (new)
-
10 medium
-
13 low
-
-
Burn rate: +9.5% cumulative
-
Schedule: ~7 days behind original plan
2. Observations
We are seeing expected onboarding effects from new team members:
-
Increased coordination overhead
-
Additional review cycles required
-
Some inconsistencies in code quality and standards
-
Higher defect introduction rate in recently developed components
3. Integration and QA Impact
-
New defects are primarily originating from recently added resources
-
QA effort has increased to validate new contributions
-
Regression cycles are taking longer than planned
4. Outlook
We expect performance to stabilize once onboarding is complete and team integration improves.
However, in the short term, this has impacted both velocity and defect levels.
5. Request
Please advise how you would like us to proceed:
-
Continue with current expanded team and allow stabilization
-
Reduce scope temporarily to improve quality
-
Adjust schedule expectations
-
Rebalance resource allocation
Best,
Julie
Attachment A – Performance Comparison
| Metric | Previous Iteration | Current Iteration |
|---|---|---|
| Velocity | 92% | 88% |
| Defects | 18 | 26 |
| High Severity | 2 | 3 |
| Burn Rate | +7.8% | +9.5% |
Attachment B – Defect Origin Analysis
-
65% of new defects linked to recently onboarded developers
-
Code review rework increasing
-
QA regression cycles extended
Student Assignment
You are the Project Manager at C-Bay.
A decision to increase resources has led to:
-
Lower velocity
-
Increased defects
-
Higher cost
-
Reduced short-term stability
You must determine:
-
Whether to continue with expanded team
-
Whether to reduce or restructure resources
-
Whether to adjust expectations
-
How to stabilize delivery without losing long-term benefits
Prepare a formal written response to Julie Rama.
Required Submission Structure
Your memorandum must include:
1️⃣ Executive Position
-
Is the project still under control?
-
Is current instability acceptable?
-
Is resource expansion strategy still valid?
2️⃣ Performance Assessment
-
Why has velocity decreased despite added resources?
-
What is the significance of increased defect rates?
-
Is this temporary or structural?
3️⃣ Resource Strategy Evaluation
-
Should new resources be retained?
-
Should onboarding approach be adjusted?
-
Should team size be reduced or rebalanced?
4️⃣ Quality & Stability Position
-
Should quality stabilization be prioritized over velocity?
-
Should scope be reduced temporarily?
-
Should additional QA controls be introduced?
5️⃣ Schedule & Budget Assessment
-
Is further schedule slip acceptable?
-
Is rising burn rate justified?
-
Should corrective cost action be taken?
6️⃣ Risk Assessment
Identify and evaluate:
-
Quality degradation risk
-
Onboarding risk
-
Budget escalation risk
-
Schedule instability risk
Assign likelihood and impact.
7️⃣ Directive to ZynoxDev
Provide a clear directive, such as:
-
Continue with expanded team and stabilize onboarding
-
Reduce scope temporarily to improve quality
-
Introduce stricter code review and QA controls
-
Rebalance resource allocation
-
Delay enhancement delivery to regain stability
Learning Focus
Scenario 14 introduces:
-
Consequences of late resource expansion
-
Onboarding and knowledge transfer challenges
-
Short-term instability vs long-term gain
-
Trade-offs between velocity and quality
-
Managing unintended consequences of decisions
Students must demonstrate:
-
Systems thinking
-
Patience in stabilization
-
Recognition of temporary vs structural issues
-
Strategic adjustment of earlier decisions
Key Insight
Adding resources does not immediately increase output.
It often:
-
Reduces efficiency temporarily
-
Introduces quality variation
-
Requires coordination overhead
Effective project management requires anticipating this effect.
This scenario reinforces:
Every decision has second-order consequences