New record
Creates one objective, requirement or constraint in the active project.
For: Product owner
Fields
| Field | How to fill it |
|---|---|
| Type | Which of the ten types the record is. |
| Code | Optional. Leave empty to generate one like FR-3A9C1E, or use your own scheme (FR-001). Must be unique in the project. |
| Title | A short name, a few words. |
| Statement | One clear, testable sentence. Say what, not how. |
| Rationale | Why the record exists. Helps reviewers and agents weigh it. |
| Acceptance criteria | A list of separate, verifiable conditions (AC1, AC2…). Each one is tracked and verified on its own. Requirements need at least one before they can be Approved or Authority; for objectives and constraints they are optional. |
| Authority state | Draft, Approved, Authority or Retired. Start with Draft if it still needs review. |
| Priority, owner, source | Importance, the accountable person or role, and where it came from (ticket, meeting, document). |
Writing good records
- One requirement per record. Split statements joined with "and".
- Avoid vague words such as "fast" or "user friendly"; give a number or a check.
- Write one condition per acceptance criterion, ideally as "given …, when …, then …". Two conditions in one row cannot be verified separately.
- Do not repeat an existing record. Search the type first.