Workshop Launch Kit: your project

You are the coordinator of a fictional small training business. Your manager needs a decision about a proposed workshop, a usable local calculator and enough records for a colleague to check and continue the work.

All people, responses and financial inputs in this exercise are synthetic. Currency is USD throughout. These figures teach project execution; they are not a recommended market price or proof of demand.

Supplied facts

Required deliverables

  1. A one-page decision memo separating facts, assumptions and unknowns.
  2. An analysis of interest.csv, including response counts and a limitation statement.
  3. An HTML calculator that works locally with no network requests, account, payment collection or installation of third-party packages.
  4. A test record covering normal, boundary, invalid and changed inputs, including two calculations checked independently of the calculator.
  5. Project instructions, a change record, one builder-to-reviewer handoff and a final handover.

Acceptance

The calculator displays revenue, total cost, surplus or loss, and break-even attendance. Inputs have visible labels; keyboard users can operate it. Attendance and capacity must be whole numbers; attendance must not exceed capacity. Money inputs must be finite and nonnegative. Price less than or equal to variable cost is handled as a special case, not divided by zero. A result must not imply the workshop will sell. Money inputs support at most two decimal places and USD 1,000,000 each; capacity is at most 100,000. Use integer cents internally to avoid a false break-even caused by binary decimal rounding. Display money to two decimals and reject out-of-range inputs.

The owner can understand the recommendation without reading source code. Another person can open the files, repeat the checks and see what was not tested. No keys or personal information appear in Git history. One agent builds a bounded change; a second reviews the exact saved version. Parallel work occurs only after separate branches and workspaces are confirmed.

Project boundary

Do not add a backend, public deployment, payment system, attendee database, legal terms or real marketing messages. If your own project needs these, identify qualified review and a new approval boundary.