Write a one-page scope with explicit exclusions

Scope protects the client and delivery team by making the promised boundary visible. Exclusions are especially important for a portfolio simulation.

Check a fictional scope

The delivery lab defines one invoice-proposal phase.

from delivery_cases import scope_case

result = scope_case()
assert result["explicit_exclusions"] == 4
assert result["production_write_excluded"] is True
assert result["scope"]["assumptions"] == ["synthetic invoices", "sandbox only"]
assert result["client_signed"] is False

Include problem/objective, users, deliverables, acceptance, in-scope data/systems, milestones, responsibilities, assumptions, exclusions, risks and change process. State production access, compliance certification, unsupported formats and operations beyond handover explicitly.

Keep it concise enough to review together. Link technical details elsewhere. Ask the decision owner to confirm or request changes; the fixture remains unsigned until a real simulation reviewer acts.

The FDE for Freshers course uses scope as an assessed client artifact.

Exercise

Write a one-page scope for your capstone, then have a peer play a stakeholder who assumes three excluded features. Revise until the boundary is unmistakable.

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 Turn a vague automation request into acceptance criteria.
• Continue with Map stakeholders and decision owners in a small project.

Reference: Scrum Guide.