Clear definitions for the terms you'll hear during any software or website project.
Scope creep is when a project grows beyond the agreed scope without a clear decision to change it.
Product discovery is the work of defining the problem, users, and constraints before committing to a build.
Acceptance criteria are the conditions that must be true for a feature to be considered done.
Edge cases are uncommon scenarios that can break a feature if they are not handled explicitly.
Delivery risk is the chance that a build slips or fails because critical dependencies were not resolved early.
MVP definition is the process of deciding what must ship first and what must wait.
A scope map is a single view of rules, edge cases, and non-goals that define what will be built.
A decision log is a running record of key product decisions and who made them.
Non-goals are explicit statements of what the product will not do in this release.
Scope freeze is the point where changes require a formal trade-off or timeline shift.
A build plan is a sequenced list of milestones that shows how scope turns into delivery.
Launch readiness is the set of operational checks that keep an MVP stable on day one.
A product brief is a one-page summary of the problem, user, and scope for a release.
