4.5.28: Scenario 27 – Process Drift Reappears and Measurable Impact Emerges
- Page ID
- 54833
\( \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 27 – Process Drift Reappears and Measurable Impact Emerges
Scenario Context
Following the first iteration under the realigned baseline:
-
Minor process deviations were observed
-
Flexibility was allowed in limited areas
-
No immediate impact was visible
However, over the next iteration cycle, these deviations have begun to accumulate again.
The project is still functioning.
But early signs of drift are now measurable.
Email from Julie Rama
Subject: Iteration Update – Emerging Variance
Hi,
I wanted to provide an update on the most recent iteration and highlight a few trends we are observing.
1. Current Status
-
Velocity: 89% of revised baseline
-
Defects: 15 open (2 medium severity)
-
Budget: +2.5% above revised projection
-
Schedule: slight delay emerging (~2–3 days)
2. Observations
We are seeing a pattern similar to earlier phases:
-
Incremental enhancements being added without full documentation
-
Backlog adjustments occurring during iterations
-
Increased coordination overhead due to informal changes
3. Impact
While no single issue is critical, the cumulative effect is now visible in:
-
Reduced velocity
-
Increased QA effort
-
Slight schedule drift
-
Additional effort not originally planned
4. Vendor Perspective
We believe this is still manageable, but it does suggest that maintaining strict process discipline may be necessary to prevent further impact.
5. Request
Please advise whether you would like to:
-
Reinforce stricter controls
-
Continue with current approach
-
Adjust execution strategy
Best,
Julie
Attachment A – Trend Comparison
| Metric | Previous Iteration | Current Iteration |
|---|---|---|
| Velocity | 93% | 89% |
| Defects | 8 | 15 |
| Budget Variance | 0% | +2.5% |
| Schedule | On track | Slight delay |
Attachment B – Identified Causes
-
Informal feature additions
-
Mid-iteration scope adjustments
-
Reduced adherence to change control
Student Assignment
You are the Project Manager at C-Bay.
After allowing limited flexibility, the project is now showing:
-
Declining performance
-
Increased defects
-
Budget and schedule drift
-
Re-emergence of earlier patterns
You must determine:
-
Whether control was insufficiently enforced
-
Whether stricter measures are now required
-
How to prevent further drift
-
How to restore discipline without disrupting progress
Prepare a formal written response to Julie Rama.
Required Submission Structure
Your memorandum must include:
1️⃣ Executive Position
-
Is the project under control?
-
Is drift occurring again?
-
Is intervention required immediately?
2️⃣ Drift Analysis
-
What patterns are repeating from earlier scenarios?
-
What caused the re-emergence of drift?
-
Was prior control strategy insufficient?
3️⃣ Control Enforcement Strategy
-
Should strict controls now be enforced?
-
Should flexibility be removed entirely?
-
Should escalation mechanisms be introduced?
4️⃣ Schedule & Budget Position
-
Is current drift acceptable?
-
Should corrective action be taken immediately?
-
Should thresholds trigger intervention?
5️⃣ Risk Assessment
Identify and evaluate:
-
Scope drift risk
-
Budget creep risk
-
Schedule instability risk
-
Governance failure risk
Assign likelihood and impact.
6️⃣ Corrective Action Plan
-
What immediate steps should be taken?
-
How will discipline be restored?
-
What controls will be enforced going forward?
7️⃣ Directive to ZynoxDev
Provide a clear directive, such as:
-
Enforce strict change control with no exceptions
-
Freeze all unapproved enhancements
-
Require backlog lock at iteration start
-
Eliminate direct stakeholder-developer communication
-
Introduce formal compliance checkpoints
Learning Focus
Scenario 27 introduces:
-
Recurrence of drift
-
Consequences of partial enforcement
-
Need for decisive intervention
-
Restoring control after slippage
-
Recognizing patterns over time
Students must demonstrate:
-
Accountability for earlier decisions
-
Strong corrective action
-
Clear enforcement strategy
-
Willingness to tighten control
Key Insight
Allowing small exceptions creates large consequences.
This scenario reinforces:
Discipline ust be enforced — not suggested.