4.5.27: 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{\ket}[1]{\left| #1 \right>}\)
\(\newcommand{\bra}[1]{\left< #1 \right|}\)
\(\newcommand{\braket}[2]{\left< #1 \vphantom{#2} \right| \left. #2 \vphantom{#1} \right>}\)
\(\newcommand{\braopket}[3]{\left< #1 \vphantom{#2}\vphantom{#3} \right| #2 \vphantom{#1}\vphantom{#3} \left| #3 \vphantom{#1}\vphantom{#2} \right>}\)
\(\newcommand{\qmvec}[1]{\mathbf{\vec{#1}}}\)
\(\newcommand{\op}[1]{\hat{\mathbf{#1}}}\)
\(\newcommand{\expect}[1]{\langle #1 \rangle}\)
\(\newcommand{\dfn}[1]{\emph{\textbf{#1}}}\)
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.
Current Performance
- Velocity: 86% of revised baseline
- Defects: 9 open (stable)
- Budget: within revised projection
- Schedule: slightly extended due to reduced throughput
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
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
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
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:
Executive Position
- Is the current control level appropriate?
- Is reduced velocity acceptable?
- Is vendor concern justified?
Control vs Efficiency Assessment
- Has control improved project stability?
- Is process overhead too high?
- Is delivery efficiency being compromised?
Process Adjustment Strategy
Choose and justify:
- Maintain strict control
- Introduce controlled flexibility
- Define exception-based process
- Adjust approval thresholds
Schedule & Delivery Position
- Is reduced velocity acceptable?
- Should throughput be improved?
- What trade-offs are acceptable?
Risk Assessment
Identify and evaluate:
- Over-control risk
- Delivery slowdown risk
- Vendor friction risk
- Re-emergence of drift risk
Assign likelihood and impact.
Vendor Relationship Strategy
- How will you address vendor concerns?
- How will you maintain alignment and motivation?
- How will you communicate process expectations?
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 is about balance.