Skip to content

User Acceptance Criteria #1

@drelliche

Description

@drelliche

When the NALMS project can achieve all of these tasks, this first version is considered done.

Learner Perspective:

  • PRIORITY 1: Up to date learner status within NALMS (i.e. opt-out). See EDU-79 and EDU-81
  • PRIORITY 1: Change/correct email address/preferred name. See EDU-82 and EDU-83
    • New form in Pipeline
  • Learner should always be able to see current version of progress form and update it. See EDU-84 and EDU-85
  • Predictable and clear communication. See EDU-85
  • Emails are reply-able. See EDU-86
  • Learners can access all modules from both pathways forms and emails. See EDU-84
  • PRIORITY 1: Once everything is marked complete, get a "completion" email and no more. See EDU-87 and EDU-88
    • Create "done" status
  • Every module must have a status. (I can't accidentally erase my progress). See EDU-84

Staff Perspective:

Pathway Creation

  • DOCUMENTATION PRIORITY 1: Any member of the staff can create a new pathway completely from a short series of complete instructions. See EDU-89
  • DOCUMENTATION PRIORITY 1: Any member of the staff can upload a new pathway to REDCap with all the alerts, notifications, etc. See EDU-90
  • New pathway creation does not interfere with existing pathways. See EDU-91
  • DOCUMENTATION PRIORITY 1: Elizabeth or Rose H can adjust email cadence, program length, etc. for a new pathway. See EDU-92

Care and Feeding of Learners

  • DOCUMENTATION PRIORITY 1: Can find any individual's record and send them their survey link. See EDU-93
  • DOCUMENTATION PRIORITY 1: Can find any individual's current status. See EDU-94
  • PRIORITY 2: Have a report of where all learners are on their pathway. See EDU-95
  • PRIORITY 2: Have a report of anyone who has marked everything complete and send them a "congrats" email. See EDU-96
  • PRIORITY 2: Have a report of anyone who hasn't updated their progress in 2 weeks. See EDU-97

Metadata

Metadata

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions