Evaluation Form: Evaluation Criteria

[r-bartlett-gsa]

User Story

As a challenge manager, in order to inform what evaluators should evaluate the submissions on, I would like to setup evaluation criteria.

Acceptance criteria:

• [ ] A challenge manager can setup one scoring criteria at the time in Evaluation Form Creation workflow by providing the following criteria information:
  • [ ] A checkbox to require evaluators to provide feedback/comments for each criteria
  • [ ] if checked will display a required open text area for the evaluator
  • [ ] Radio buttons to indicate scale type, #69 (required field)
  • [ ] An input field for Criteria title (required field)
  • [ ] A text field for Criteria details / description (required field)
  • [ ] A numerical input field for Criteria Points / weight (required field)
  • [ ] The system validates if an input provided by a challenge manager is numerical
  • [ ] The input is used to calculate the criteria score and total score, https://github.com/GSA/Challenge_platform/issues/71
  • [ ] Radio buttons for scoring type and conditional fields for rating scale options, #68 (required field)
• [ ] A challenge manager can add additional criteria and go through criteria setup steps as outlined above for each one
• [ ] Created criteria options can be edited and/or deleted while the form is in draft

Development tasks:

• [ ] Task 1
• [ ] Task 2

Definition of Done

Doing (dev team)

• [ ] Code complete
• [ ] Code is organized appropriately
• [ ] Any known trade offs are documented in the associated GH issue
• [ ] Code is documented, modules, shared functions, etc.
• [ ] Automated testing has been added or updated in response to changes in this PR
• [ ] The feature is smoke tested to confirm it meets requirements
• [ ] Database changes have been peer reviewed for index changes and performance bottlenecks
• [ ] PR that changes or adds UI
  • [ ] include a screenshot of the WAVE report for the altered pages
  • [ ] Confirm changes were validated for mobile responsiveness
• [ ] PR approved / Peer reviewed

• [ ] Move card to testing column in the board

  Testing (dev team)

• [ ] Security scans passed
• [ ] Automate accessibility tests passed
• [ ] Build process and deployment is automated and repeatable
• [ ] Feature toggles if appropriate
• [ ] Deploy to staging

Staging

• [ ] Accessibility tested (Marni)
  • [ ] Keyboard navigation
  • [ ] Focus confirmed
  • [ ] Color contrast compliance
  • [ ] Screen reader testing
• [ ] Usability testing: mobile and desktop (Tracy or Marni)
• [ ] Cross browser testing (tool to be determined) (Tracy or Marni)
  • [ ] UI rendering is performant
• [ ] AC review (Renata)
• [ ] Deploy to production (production-like environment for eval capability) (dev team)

• [ ] Move to production column in the board

  Production

• [ ] User and security documentation has been reviewed for necessary updates (Renata/Tracy/Dev team)
• [ ] PO / PM approved (Jarah or Renata)
• [ ] AC is met and it works as expected (Jarah or Renata)
• [ ] Move to done column in the board (Jarah or Renata)

[r-bartlett-gsa]