Skip to main content
Workforce LibreTexts

4.5.6: Scenario 5 – Executive Pressure and Vendor Defensiveness

  1. Last updated
  2. Save as PDF
  • Page ID
    54811

    • \( \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 5 – Executive Pressure and Vendor Defensiveness

    Scenario Context

    Project Reckon is in the final phase of preparing Release Candidate 1 (RC1).

    In previous scenarios:

    • A change order request was submitted for reporting enhancements

    • Burn rate exceeded monthly tolerance

    • Minor schedule slip emerged

    • Scope boundaries were actively debated

    Since then, internal visibility has increased.

    A senior executive at C-Bay has requested a preview demonstration for an upcoming stakeholder meeting.

    At the same time, ZynoxDev has begun to respond more defensively to recent project direction and scope decisions.

    The project is not failing.

    However, alignment is becoming strained.

    Email from Julie Rama

    Subject: RC1 Readiness – Stakeholder Demo and Alignment Concerns

    Hi,

    I wanted to provide a quick update as we approach RC1 readiness and flag a couple of points for alignment.

    1. Executive Demo Request

    We understand that a senior stakeholder has requested a preview of Reckon for an upcoming executive session.

    To support this, your team has asked whether we can include elements of the enhanced reporting functionality for demonstration purposes.

    As discussed previously, these features are not part of the approved scope for RC1 and would require additional development effort.

    While we are open to supporting demo scenarios, incorporating partial functionality at this stage may introduce instability into the RC1 build.

    2. Current Delivery Position

    • Velocity: 90% of baseline

    • Defects: 16 open (1 high, integration-related)

    • Burn rate: +6.8% (monthly)

    • Schedule: ~5 days behind original RC1 plan

    We are continuing stabilization and believe RC1 remains achievable within tolerance if scope remains unchanged.

    3. Alignment Concern

    I would also like to note that recent discussions around scope, change control, and cost adjustments have introduced some uncertainty within our delivery teams.

    There is concern that expectations may be shifting without formal agreement, which makes planning more difficult.

    We remain committed to delivering Reckon successfully, but would appreciate clear alignment on:

    • Scope boundaries for RC1

    • Expectations for executive demo content

    • Whether any additional features should be prioritized

    Please advise how you would like us to proceed so we can ensure both delivery stability and stakeholder expectations are met.

    Best,
    Julie

    Attachment A – Executive Demo Request Summary

    • Requested by: Senior C-Bay Executive

    • Purpose: Internal stakeholder presentation

    • Requested capability:

      • Enhanced reporting view

      • Dynamic filtering preview

    • Timeline: Within current RC1 window

    Attachment B – Current Project Metrics

    Category Status
    Velocity 90% of baseline
    Defects Declining, but integration issue remains
    Burn Rate +6.8% monthly
    Schedule Slight delay (within tolerance)

    Student Assignment

    You are the Project Manager at C-Bay.

    You are now facing:

    1. Internal executive pressure to enhance the demo experience

    2. Vendor defensiveness due to perceived scope instability

    3. Ongoing budget and schedule pressure

    You must:

    • Protect delivery stability

    • Manage internal expectations

    • Maintain vendor alignment

    • Avoid informal scope expansion

    • Ensure clear communication

    Prepare a formal written response to Julie Rama.

    Required Submission Structure

    Your memorandum must include:

    1️⃣ Executive Position

    • Overall project health

    • Position on executive demo request

    • Position on vendor concerns

    2️⃣ Scope & Stakeholder Management

    • Should reporting enhancements be included in demo?

    • Should demo differ from production scope?

    • How should executive expectations be managed?

    3️⃣ Vendor Relationship Management

    • How should vendor defensiveness be addressed?

    • Is Julie’s concern valid?

    • How will you reinforce alignment without weakening authority?

    4️⃣ Schedule & Budget Position

    • Is current schedule slip acceptable?

    • Is burn rate trending into risk?

    • Should stabilization be prioritized over demo enhancement?

    5️⃣ Risk Assessment

    Identify and evaluate:

    • Scope creep risk

    • Stakeholder expectation risk

    • Vendor relationship risk

    • Schedule and budget risk

    Assign likelihood and impact.

    6️⃣ Directive to ZynoxDev

    Provide a clear directive, such as:

    • Maintain current scope and stabilize RC1

    • Provide demo workaround without changing core build

    • Do not include unapproved features in production release

    • Align internal messaging with agreed scope

    • Provide controlled demo dataset or mock functionality

    Your directive must balance:

    • Delivery integrity

    • Stakeholder expectations

    • Vendor confidence

    Learning Focus

    Scenario 5 introduces:

    • Internal vs external pressure management

    • Maintaining authority without escalation

    • Handling vendor defensiveness professionally

    • Avoiding informal scope expansion under executive pressure

    • Differentiating demo needs vs product reality

    Students must demonstrate:

    • Strategic communication

    • Emotional neutrality

    • Scope discipline under pressure

    • Vendor alignment leadership

    This scenario marks a shift from technical and financial management to organizational and political management.

    4.5.6: Scenario 5 – Executive Pressure and Vendor Defensiveness is shared under a CC BY 4.0 license and was authored, remixed, and/or curated by LibreTexts.