4.11 Application security headers

[nickaddy]

Background

See pages 34-36 of report.

User Story

As user, I would like functionality so that benefit.
Users are: Candidate, Admin, Assessor, QT participant, Panellist, Digital team.

Benefit(s) to user (if not already clear from User story)

Feature(s) Description

Clearly describe the new functionality/change(s) to existing functionality.
Include a link to a Miro board/image if appropriate.

• Feature

Acceptance Criteria

Specify the requirements of the primary user(s) for the change, update, or new feature - use the format:
It's done when...

Definition of Done

• User stories/acceptance criteria met
• Internal reviews passed (feedback actioned)
• User testing passed
• Relevant technical documentation updated
• User guidance updated
• Deployed and merged without errors

User Testing Steps

Specify for users what is being tested (but not how to test it.)

Feature Champion

[drieJAC]

Was a DP ticket