4.5.14: Scenario 13 – Vendor Capacity Constraints and Resource Allocation Conflict

Scenario 13 – Vendor Capacity Constraints and Resource Allocation Conflict

---

Scenario Context

Following RC1 feedback and stakeholder requests, the enhancement backlog for Project Reckon has expanded.

Several enhancements have been discussed for prioritization, including:

• Reporting flexibility

• UI consistency improvements

• Performance optimizations

ZynoxDev has reviewed the updated backlog and is now raising concerns regarding resource capacity.

The project is not over budget in a critical way, and schedule remains within tolerance, but resource allocation is becoming a limiting factor.

---

Email from Julie Rama

Subject: Resource Allocation Constraints – Backlog Prioritization Required

Hi,

Following the recent discussions around prioritizing post-RC1 enhancements, we have completed an internal review of our current capacity and delivery commitments.

I wanted to share an important update regarding resource allocation.

---

1. Current Capacity

Our current team allocation was planned based on the original project scope and stabilization activities following RC1.

Given the recent increase in enhancement requests, we are now approaching capacity limits in the following areas:

• Development bandwidth (particularly reporting and UI modules)

• QA coverage for expanded regression cycles

---

2. Key Constraint

At this stage, we are not able to:

• Maintain current stabilization efforts

• Deliver all requested enhancements

• Preserve existing schedule commitments

— simultaneously.

Trade-offs will be required.

---

3. Available Options

From our perspective, the following options are available:

Option A:
Maintain current scope and stabilization focus
→ No additional enhancements in next iteration

Option B:
Prioritize selected enhancements
→ Defer other backlog items

Option C:
Increase team capacity
→ Additional cost and onboarding time

---

4. Impact Considerations

• Increasing resources may introduce onboarding inefficiencies

• Reprioritizing scope may impact stakeholder expectations

• Maintaining current course may delay perceived product improvements

---

5. Request

We need your direction on how you would like to proceed.

Best,
Julie

---

Attachment A – Resource Allocation Snapshot

Area	Capacity	Current Load	Status
Development	100%	95%	Near Limit
QA	100%	110%	Over Capacity
Architecture Support	100%	85%	Stable

---

Attachment B – Enhancement Backlog

Feature	Priority	Effort Estimate
Dynamic Reporting Filters	High	Medium
Custom Views	High	Medium
UI Consistency Improvements	Medium	Low
Performance Optimization	High	Medium

---

Student Assignment

You are the Project Manager at C-Bay.

ZynoxDev has made it clear:

Not everything can be done at once.

You must now make explicit decisions regarding:

• Scope prioritization

• Resource expansion

• Schedule implications

• Cost impact

You must determine how to balance:

• Stakeholder expectations

• Vendor capacity

• Delivery stability

Prepare a formal written response to Julie Rama.

---

Required Submission Structure

Your memorandum must include:

---

1️⃣ Executive Position

• How should the project proceed given capacity constraints?

• Which priority should dominate: stability, enhancements, or expansion?

---

2️⃣ Scope Prioritization Decision

• Which enhancements should be prioritized?

• Which should be deferred?

• Should scope be reduced or rebalanced?

Provide a clear prioritization strategy.

---

3️⃣ Resource Strategy

• Should additional resources be added?

• Are onboarding risks acceptable?

• Should capacity constraints be accepted instead?

---

4️⃣ Schedule & Budget Assessment

• Will prioritization affect schedule?

• Will adding resources affect budget trajectory?

• What trade-offs are acceptable?

---

5️⃣ Risk Assessment

Identify and evaluate:

• Capacity risk

• Schedule disruption risk

• Budget escalation risk

• Product stability risk

Assign likelihood and impact.

---

6️⃣ Stakeholder Management Strategy

• How will you communicate prioritization decisions internally?

• How will you manage expectations around delayed enhancements?

---

7️⃣ Directive to ZynoxDev

Provide a clear directive, such as:

• Prioritize specific enhancements and defer others

• Maintain stabilization and delay enhancements

• Increase resources under defined conditions

• Rebalance workload across iterations

---

Learning Focus

Scenario 13 introduces:

• Capacity constraints in outsourced development

• Explicit trade-off decision-making

• Prioritization discipline under pressure

• Resource vs cost vs schedule balancing

• Managing finite delivery capability

Students must demonstrate:

• Strategic prioritization

• Realistic resource thinking

• Controlled decision-making

• Ability to say “no” or “not now”

---

Key Insight

Every project eventually reaches a point where:

Capacity defines reality.

Not:

• Requirements

• Ambition

• Stakeholder desire

---

This scenario teaches:

Project management is the art of choosing what not to do — right now.