Handle a client request that changes the scope

“Can it also update accounting?” sounds small but changes permissions, failure impact, testing and rollback. A professional response makes that impact reviewable.

Evaluate a fictional change

The delivery lab records an authored request.

from delivery_cases import scope_change_case

result = scope_change_case()
assert result["impact_complete"] is True
assert result["request"]["impact"]["days"] == 5
assert result["silent_scope_expansion"] is False
assert result["approved_for_current_scope"] is False

Clarify requested outcome and urgency. Compare with signed scope, then assess architecture, data/access, security, tests, operations, cost and timeline. Offer options: replace lower-value work, extend phase, prototype separately or defer.

Record request, impact, recommendation, approver and decision. Do not start on verbal enthusiasm when the change introduces sensitive writes. Update acceptance, risk, estimate and runbook after approval.

The FDE for Freshers course practises “always be scoping” through client simulations.

Exercise

Introduce a mid-capstone write request. Produce a one-page change record and defend a defer/approve decision to a mock sponsor.

Continue learning

This article is part of the FDE career entry and client-delivery practice sequence. Use the neighbouring tasks when you need the prerequisite or the next application.

• Review the prerequisite or neighbouring task in Prepare a live demo with a recovery plan.
• Continue with Write a clear weekly project update.

Reference: Agile Manifesto principles.