4.5.4: Scenario 3 – Financial Strain and Emerging Scope Pressure

Scenario 3 – Financial Strain and Emerging Scope Pressure

---

Scenario Context

Project Reckon has completed Iteration 4 and is preparing for Release Candidate 1 (RC1).

In previous iterations, defect clustering in the Synchronization Engine required additional QA effort. ZynoxDev has increased testing intensity to stabilize integration behavior.

At the same time, an internal stakeholder at C-Bay has requested enhancement to reporting functionality after viewing the RC1 demo.

The combination of added effort and emerging feature pressure is beginning to affect burn rate and staffing alignment.

This scenario examines financial discipline, scope containment, and early change order management.

---

Email from Julie Rama

Subject: Iteration 4 Update – Resource Adjustment and Reporting Enhancement

Hi,

We’ve completed Iteration 4 development and are finalizing internal stabilization before RC1 freeze.

I want to raise two items for your review:

1. QA Resource Increase

Due to the integration defect cluster identified in Iteration 3, we temporarily increased QA allocation by approximately 25% during this sprint to accelerate regression coverage and concurrency testing.

This has resulted in:

• Burn rate: +6.4% over projected staffing curve

• Development hours stable

• QA hours significantly above baseline

While total project burn remains within overall tolerance, monthly variance now exceeds the ±5% target.

We believe this increased QA effort is temporary and necessary to stabilize RC1.

---

2. Reporting Enhancement Request

During the RC1 preview demo, a senior stakeholder asked whether the Reporting Manager could include:

• Dynamic filtering by role

• Export of filtered datasets

• Timestamped audit of report generation

These features were not explicitly defined in the original URD.

From a development perspective, implementing these capabilities in RC1 would require:

• Additional design effort

• Additional QA regression

• Potential 1-week milestone extension

Please advise how you would like us to proceed regarding both the QA allocation variance and the reporting enhancement request.

Best,
Julie

---

Attachment A – Budget Burn Summary

Category	Planned (Cumulative)	Actual (Cumulative)	Variance
Development Hours	1,280	1,296	+1.2%
QA Hours	460	582	+26.5%
Total Burn	—	+6.4% (Month 4)

---

Attachment B – Schedule Status

Milestone	Planned Date	Status
Iteration 4 Complete	On Schedule	Achieved
RC1 Freeze	On Schedule	At Risk if reporting enhancement added

---

Attachment C – Defect Trend

Defect count declining overall.
Integration defects now mostly medium and low severity.
Concurrency testing coverage increased.

---

Student Assignment

You are the Project Manager at C-Bay.

Two simultaneous pressures now exist:

1. Burn rate exceeds ±5% monthly tolerance due to increased QA effort.

2. A senior stakeholder is implicitly requesting additional reporting functionality not clearly defined in the URD.

You must determine:

• Whether QA overage is acceptable or requires financial intervention.

• Whether reporting enhancements constitute scope expansion.

• Whether change control should be initiated.

• Whether schedule extension is acceptable.

• Whether RC1 freeze date should remain fixed.

• How to respond without damaging vendor partnership or internal stakeholder relationships.

Prepare a formal written response to Julie Rama.

---

Required Submission Structure

Your memorandum must include the following:

---

1️⃣ Executive Position

• Overall project health assessment

• Statement on financial strain

• Position on reporting enhancement

---

2️⃣ Budget Assessment

• Is +6.4% burn acceptable?

• Is increased QA effort justified?

• Should corrective action or financial review occur?

• Does this require formal variance approval?

---

3️⃣ Scope & Change Control Decision

• Do reporting enhancements fall within original scope?

• Should they be deferred to a later release?

• Should formal change control be initiated?

• Should impact analysis be required before authorization?

---

4️⃣ Schedule Position

• Should RC1 milestone remain unchanged?

• Is 1-week extension acceptable?

• Should schedule trade-offs be considered?

---

5️⃣ Risk Assessment

Identify and classify:

• Budget risk

• Scope creep risk

• Schedule risk

• Stakeholder management risk

Assign likelihood and impact.

---

6️⃣ Directive to ZynoxDev

Provide precise instructions, such as:

• Continue elevated QA temporarily with documented financial tracking.

• Freeze additional reporting features until formal change request submitted.

• Provide cost and schedule impact analysis before scope expansion.

• Maintain RC1 freeze date.

• Present alternative phased delivery plan.

Your directive must balance financial discipline, delivery stability, and stakeholder expectations.

---

Learning Focus

Scenario 3 introduces multi-dimensional tension:

• Financial strain without crisis

• Scope expansion pressure from internal leadership

• QA trade-off decisions

• Schedule stability vs enhancement temptation

• Early change order governance

Students must demonstrate:

• Proportional financial oversight

• Structured change control discipline

• Strategic stakeholder management

• Non-reactive decision-making