4.5.29: Scenario 28 – Control Enforcement and Vendor Friction
- Page ID
- 54834
\( \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 28 – Control Enforcement and Vendor Friction
Scenario Context
Following the reintroduction of strict controls in Scenario 27:
-
Formal change control has been enforced
-
Backlog is locked at iteration start
-
Informal feature additions have been restricted
-
Stakeholder-developer direct communication has been limited
These actions have successfully reduced scope drift.
However, they have also introduced new challenges.
Email from Julie Rama
Subject: Execution Update – Impact of Control Measures
Hi,
I wanted to provide an update following the implementation of stricter process controls.
1. Current Performance
-
Velocity: 86% of revised baseline
-
Defects: 9 open (stable)
-
Budget: within revised projection
-
Schedule: slightly extended due to reduced throughput
2. Observations
We are seeing the following effects:
-
Improved control over scope and backlog
-
Reduced unplanned work
-
Slower turnaround for stakeholder requests
-
Increased process overhead for approvals and documentation
3. Team Feedback
Our delivery team has noted:
-
Reduced flexibility in handling small changes
-
Increased administrative effort
-
Slower decision cycles for minor adjustments
There is concern that:
-
The current level of control may be impacting delivery efficiency
-
Team responsiveness is reduced
4. Vendor Perspective
We fully understand the need for discipline.
However, we believe there may be an opportunity to:
-
Introduce controlled flexibility
-
Reduce friction for low-risk changes
-
Improve execution speed while maintaining oversight
5. Request
Please advise whether you would like to:
-
Maintain strict controls
-
Introduce controlled flexibility
-
Adjust process to improve efficiency
Best,
Julie
Attachment A – Performance Comparison
| Metric | Pre-Control | Post-Control |
|---|---|---|
| Velocity | 89% | 86% |
| Defects | 15 | 9 |
| Scope Drift | Present | Controlled |
| Process Overhead | Low | High |
Attachment B – Team Feedback Summary
-
“Too many approvals for small changes”
-
“Slower iteration cycles”
-
“Less ability to respond quickly to stakeholders”
Student Assignment
You are the Project Manager at C-Bay.
Your decision to enforce strict control has:
-
Reduced drift
-
Improved stability
-
Increased process overhead
-
Slowed execution
You must now determine:
-
Whether current controls are too restrictive
-
Whether controlled flexibility should be introduced
-
How to balance discipline with efficiency
-
How to maintain vendor alignment
Prepare a formal written response to Julie Rama.
Required Submission Structure
Your memorandum must include:
1️⃣ Executive Position
-
Is the current control level appropriate?
-
Is reduced velocity acceptable?
-
Is vendor concern justified?
2️⃣ Control vs Efficiency Assessment
-
Has control improved project stability?
-
Is process overhead too high?
-
Is delivery efficiency being compromised?
3️⃣ Process Adjustment Strategy
Choose and justify:
-
Maintain strict control
-
Introduce controlled flexibility
-
Define exception-based process
-
Adjust approval thresholds
4️⃣ Schedule & Delivery Position
-
Is reduced velocity acceptable?
-
Should throughput be improved?
-
What trade-offs are acceptable?
5️⃣ Risk Assessment
Identify and evaluate:
-
Over-control risk
-
Delivery slowdown risk
-
Vendor friction risk
-
Re-emergence of drift risk
Assign likelihood and impact.
6️⃣ Vendor Relationship Strategy
-
How will you address vendor concerns?
-
How will you maintain alignment and motivation?
-
How will you communicate process expectations?
7️⃣ Directive to ZynoxDev
Provide a clear directive, such as:
-
Maintain strict controls with minor adjustments
-
Introduce defined low-risk exception process
-
Allow limited flexibility for small changes
-
Adjust approval process for efficiency
-
Maintain discipline but streamline execution
Learning Focus
Scenario 28 introduces:
-
Trade-offs between control and agility
-
Managing process overhead
-
Balancing discipline with execution speed
-
Vendor relationship dynamics under constraint
-
Refining governance models
Students must demonstrate:
-
Balanced judgment
-
Process design thinking
-
Awareness of second-order effects
-
Ability to fine-tune controls
Key Insight
Too little control creates chaos.
Too much control creates friction.
This scenario reinforces:
Effective project management is not about extremes —
it isbot balance.