Requirements

What done means for a feature, and how Iron Octopus verifies each one.

Requirements define what done means for a feature, as represented by its acceptance criteria. Iron Octopus writes them into the feature’s plan, you approve them with the plan, and nothing counts as done until every required one is verified, with the evidence saved and auditable.

What a requirement contains

• The requirement itself, in plain words. For example: “A client sees only their own bookings.”
• Required or optional. Only required requirements decide whether a feature can be released.
• How it will be verified, chosen when the feature is planned.
• Its verdict and evidence, once it’s been checked.

How requirements are verified

Each requirement is verified in the way that fits it:

Method	What Iron Octopus checks
Automated test	Runs a test and records the result.
Code review	Reviews the code that implements it.
Source inspection	Inspects the repository, such as files or configuration.
Artifact review	Reviews something the work produced, such as a document.
Operational check	Checks behaviour in a running environment.

By default, Iron Octopus verifies requirements by reviewing the work. Where a requirement calls for a test or a running environment, the page shows whether that evidence was recorded. Anything Iron Octopus can’t verify comes to you.

Verdicts

Verdict	What it means
Satisfied	Verified, with evidence recorded.
Not satisfied	Checked and found short. The work goes back for more effort.
Blocked	Couldn’t be checked yet.

If the work changes after a requirement was verified, it’s marked as awaiting re-evaluation and checked again.

Where you see it

• Under Acceptance criteria on the feature’s page, with each verdict and its evidence.
• As progress on your Home page, such as “11 of 12 acceptance criteria met”.

What you can do

• Review the requirements when you approve a feature’s plan.
• Read the verdict and evidence for each one.
• Decide on anything Iron Octopus couldn’t verify.