A review of the Good Character Guidance has recently taken place, the resulting impact is that there will be amendments required to some of the questions asked of candidates in the character section of the application form to align with the changes. The aim would be for the new Good Character Guidance to apply to all applications made from on or around 1 September 2024; ideally on a date where no exercise is open for applications, so that it is clear which exercises are subject to the old Guidance and which to the new.
NOTE: Companion tickets for application view and application edit may need to be created; a companion ticket for Apply will certainly need to be created.
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.)
Background
A review of the Good Character Guidance has recently taken place, the resulting impact is that there will be amendments required to some of the questions asked of candidates in the character section of the application form to align with the changes. The aim would be for the new Good Character Guidance to apply to all applications made from on or around 1 September 2024; ideally on a date where no exercise is open for applications, so that it is clear which exercises are subject to the old Guidance and which to the new.
NOTE: Companion tickets for application view and application edit may need to be created; a companion ticket for Apply will certainly need to be created.
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.
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 Testing Steps
Specify for users what is being tested (but not how to test it.)
Feature Champion