Product scoping
The MVP Scoping Worksheet
Turn an idea into one useful flow, clear exclusions, and checks you can actually run.
Define the first useful version
Describe one person, one situation, and one outcome. A first version should let you test whether that outcome matters before you expand the product.
Use the worksheet below without an account. Your entries stay in this page; they are not submitted to Racoben. Download a copy before leaving.
Your five-part worksheet
Write here or take a blank copy with you. No sign-in is needed. Your notes stay in this page’s memory; they are not saved or sent to Racoben.
Download your notes before refreshing or leaving. Opening another page does not carry them into a project request.
Discuss this scope with our team →A completed fictional example
Illustrative concept: a repair shop pickup tracker. This is a fictional example, not a Racoben customer or a claim about a shipped product.
Intended user: a repair shop receptionist answering customers who ask whether a repaired item is ready.
Core flow: find a repair by its reference → mark it ready → see it in the pickup list → mark it collected.
Must-haves: staff sign-in; a repair reference and status; a ready-for-pickup list. Each repair belongs to one shop.
Exclusions: payments, text messages, customer accounts, inventory tracking, and multi-location reporting.
Acceptance checks: staff from another shop cannot read the repair; marking a repair ready adds it to the pickup list; marking it collected removes it; the core flow works with keyboard input and on a phone.
Review the boundaries together
Ask what happens when the record is missing, a required value is wrong, or a connection fails. A happy-path demonstration alone does not describe the whole agreed experience.
Put dependencies beside the scope: who supplies accounts, hosting, data, content, and access? Agree how changes will be handled. The worksheet prepares a conversation; the signed project agreement defines the commitment.