Skip to content
Trevin Nimaladasa

TEMPLATESJIRA · REQ

Requirement

A clear, measurable, testable statement of a business need with dependencies and constraints.

Paste the blank into the ticket description and overwrite the [brackets].

  1. 01Summary

    A short title that names the capability. Write it as something the system or business must do, not as a solution.

    [Who / what] must be able to [capability]

    Example

    Customers must be able to reset their password from the mobile app

  2. 02Business Need

    Say what problem or opportunity this answers, and for whom. Give a fact or a number so a reader can judge the priority.

    [Who] needs this because [problem or opportunity]. Evidence: [number, complaint, deadline].

    Example

    Locked-out customers can only recover access by calling support. Password resets are 31% of contacts and cost about 9 minutes each.

  3. 03Description

    Write what the thing must do in plain terms. One requirement per ticket. Use "must" for the mandatory and say how you'd measure it. Avoid design words like "button" or "dropdown".

    The [system / process] must [behaviour] when [condition], so that [measurable result].

    Example

    The mobile app must let a customer request a password reset with their registered email and complete it from the emailed link, so that 90% of resets finish without contacting support.

  4. 04Dependencies / Constraints

    Separate what must exist first from what limits the solution (policy, technology, budget, regulation). Mark assumptions as assumptions.

    - Dependency: [what must exist first]
- Constraint: [limit on the solution]
- Assumption: [not yet confirmed]

    Example

    • Dependency: identity provider supports reset tokens
    • Constraint: must follow the group password policy (12+ characters)
    • Assumption: customers still have access to their registered email

  5. 05Acceptance Criteria

    These are about the requirement itself, not the build. Is it clear, testable, agreed? Edit to fit your review process.

    - [ ] Requirement is clear, measurable, and testable.
- [ ] Requirement is reviewed and validated with stakeholders.
- [ ] Requirement is approved by the Product Owner or Business Lead.

    Example

    • "90% complete without contacting support" is measurable from existing analytics.
    • Reviewed with Support and Security on 4 Nov.
    • Approved by the Head of Digital on 6 Nov.

  6. 06Definition of Done (DoD)

    List where it's stored, what it links to, and who signed it off. A requirement with no links is not traceable.

    - [ ] Requirement is documented and stored in the agreed repository.
- [ ] Linked to relevant design, development, or testing tickets.
- [ ] Follow-on actions or changes are created as separate Jira items.
- [ ] Requirement has sign-off from the appropriate authority.

    Example

    • Stored in the requirements register, version 1.0.
    • Linked to US-318, DES-45 and TC-118.
    • Open question on SMS fallback raised as TSK-902.
    • Signed off by the Head of Digital.