4.5.26: Scenario 25 – Baseline Reset and Contract Realignment

Scenario 25 – Baseline Reset and Contract Realignment

---

Scenario Context

Following scope reconciliation and stakeholder conflict in Scenario 24, it is now clear that:

• The original scope baseline is no longer accurate

• Informal enhancements have become embedded in the system

• Stakeholder expectations have evolved

• Budget and schedule assumptions have shifted

C-Bay has initiated a formal realignment effort to:

• Reset scope baseline

• Clarify deliverables

• Reconcile cost and schedule

• Establish clear control moving forward

ZynoxDev has responded with a formal proposal.

---

Email from Julie Rama

Subject: Project Realignment Proposal – Scope, Schedule, and Cost

Hi,

Following the recent scope reconciliation discussions, we have prepared a proposal to align the project moving forward.

---

1. Proposed Scope Baseline

We recommend redefining the project scope as follows:

• Core Features (Original Scope) → Completed

• Enhancements (Previously Informal) → Included as formal scope

• Partial Features → Completed or removed based on prioritization

This reflects the system as it currently exists and stakeholder expectations.

---

2. Schedule Realignment

To accommodate the expanded scope and stabilization efforts:

• Revised delivery timeline: +2 weeks beyond original plan

• Adjusted milestone checkpoints for future iterations

---

3. Budget Adjustment

Based on current effort and scope expansion:

• Proposed budget increase: +12–14%

• Reflects:

  • Additional development effort

  • Increased QA cycles

  • Refactoring and stabilization work

---

4. Control Measures

To prevent further drift, we propose:

• Strict change control for all future enhancements

• Formal backlog prioritization reviews

• Defined iteration scope boundaries

---

5. Request

Please review and confirm:

• Acceptance of revised scope baseline

• Approval of schedule adjustment

• Approval of budget realignment

We believe this will establish a stable foundation moving forward.

Best,
Julie

---

Attachment A – Realignment Summary

Area	Original	Revised
Scope	URD-defined	Expanded (includes enhancements)
Schedule	Original timeline	+2 weeks
Budget	Baseline	+12–14%

---

Attachment B – Control Measures

• Formal change request process required for all new features

• Backlog review at start of each iteration

• No in-iteration scope adjustments allowed

---

Student Assignment

You are the Project Manager at C-Bay.

You must now decide whether to:

• Accept the proposed realignment

• Modify the proposal

• Reject elements of the proposal

This decision will define:

• The new baseline for the project

• The credibility of project control moving forward

• The relationship with ZynoxDev

You must evaluate:

• Whether the proposed scope is acceptable

• Whether budget increase is justified

• Whether schedule adjustment is reasonable

• Whether control measures are sufficient

Prepare a formal written response to Julie Rama.

---

Required Submission Structure

Your memorandum must include:

---

1️⃣ Executive Position

• Do you accept the realignment proposal?

• What elements do you approve or reject?

• Is the project now under control?

---

2️⃣ Scope Decision

• Should all enhancements be formalized into scope?

• Should any features be removed or deferred?

• Is the revised scope appropriate?

---

3️⃣ Budget & Schedule Decision

• Is +12–14% budget increase justified?

• Is a +2 week delay acceptable?

• Should adjustments be negotiated?

---

4️⃣ Contract & Control Alignment

• Are proposed control measures sufficient?

• Should additional controls be introduced?

• How will future drift be prevented?

---

5️⃣ Risk Assessment

Identify and evaluate:

• Budget overrun risk

• Schedule extension risk

• Scope misalignment risk

• Governance failure risk

Assign likelihood and impact.

---

6️⃣ Strategic Positioning

• How will you communicate this realignment internally?

• How will you justify the changes to leadership?

• How will you restore confidence in project control?

---

7️⃣ Directive to ZynoxDev

Provide a clear directive, such as:

• Approve full realignment

• Approve with modifications

• Reject certain scope elements

• Require revised proposal

• Implement additional governance controls

---

Learning Focus

Scenario 25 introduces:

• Formal baseline reset

• Contract realignment

• Converting informal history into structured agreement

• Negotiation of cost, scope, and schedule simultaneously

• Establishing control after drift

Students must demonstrate:

• Strategic negotiation

• Decision ownership

• Balance between acceptance and control

• Long-term thinking

---

Key Insight

A project can only be controlled once reality is acknowledged.

---

This scenario reinforces:

You cannot manage what is no longer aligned with the plan.

You must:

• Update the plan

• Or restore the plan

---

This marks a major turning point in the practicum.