The MVP Scoping Worksheet

Part 1 - The Riskiest Assumption

Every idea rests on assumptions. Name the one that, if wrong, sinks the whole thing. That's what your MVP must test.

• The riskiest assumption behind my idea is: ____________________
• If this assumption is wrong, the idea fails because: ____________________
• The fastest way to test it with real users is: ____________________

Part 2 - User, Problem, and Outcome

Describe who has the problem, what they are trying to do, and the useful outcome they need. Keep the first version focused enough to check with real users.

• The user or role is: ____________________
• Their current problem is: ____________________
• The outcome they need is: ____________________
• The moment they know it worked is: ____________________

Part 3 - Current Workaround and Dependencies

Write down what happens today and what the first version depends on. This exposes hidden work before it becomes a delivery surprise.

• The current workaround is: ____________________
• The system, vendor, data, or access this depends on is: ____________________
• The riskiest dependency to confirm is: ____________________

Part 4 - Required States, Roles, and Permissions

Describe the states the workflow can be in and who can see or change each state. Include the permission boundary that must be respected.

• The states or stages are: ____________________
• The roles or people involved are: ____________________
• Each role can see or change: ____________________
• The data that must stay private or isolated is: ____________________

Part 5 - Acceptance Checks

List the concrete, testable statements that define done. Use as many checks as the agreed outcome needs, and make each one a single checkable sentence.

• A user can complete the intended outcome: ____________________
• The workflow handles the required success state: ____________________
• The workflow handles the required error or empty state: ____________________
• The right role can access the right information: ____________________
• The handover or release check is: ____________________

Part 6 - Exclusions and Sensitive Data

Name what is deliberately out of scope and identify sensitive data before implementation. A smaller first release is easier to review and safer to operate.

• Not building yet: ____________________
• Not configuring or automating yet: ____________________
• Sensitive or regulated data involved: ____________________
• The data that must never be pasted into a planning form is: ____________________

Part 7 - Inputs, Timing, and Contingency

Record what the client must provide, what timing depends on, and what happens if an input is late or changes. Use this to estimate a schedule with contingency rather than to promise a deadline.

• Client inputs or decisions required are: ____________________
• The schedule depends on: ____________________
• If an input is late or changes, the contingency is: ____________________
• The next decision point is: ____________________

Decision Rule

A scope is ready for a planning conversation when the user, problem, outcome, dependencies, acceptance checks, exclusions, sensitive data, and timing assumptions are clear. If uncertainty remains, use Technical Discovery or a focused review before committing to implementation.