Free video · E04
Scoping: From a vague request to a scope package
Chinese narration · Chinese captions · 11:13 · Video published on
This series uses AI-assisted voice narration; rely on the page disclosures and text curriculum for the content boundary. Examples are teaching scenarios, not evidence of customer outcomes.
Episode summary
Use a fictional borrowing-request scenario to clarify events, roles, data access and scope before coding. Combine interviews, decision records and feasibility checks into a scoping pack instead of asking AI to guess the workflow.
- Trace business events to actors, triggers, handoffs and exceptions before listing features.
- Record scope disagreements, decisions and reasons. Inventory data sources, access methods, approvers, freshness and usage restrictions.
- Ask whether the problem is real, data is accessible and the solution can be validated. Processes, schedules and cost comparisons are teaching discussion, not universal standards or outcome promises.
This is an editorial learning summary, not a transcript. Check the text lessons for conceptual boundaries.
Practice after watching
Using synthetic equipment tickets, document the problem, three interview groups, data permissions and pause conditions. Mark unknowns rather than inventing customer facts.
Open the exercise, example and reference →