Skip to content

Document procedures for reviewing an interview for maintenance/updates #450

Open

Description

@samglover

Interviews need maintenance. Our plan is to check live interviews annually, and we have a basic checklist in our recurring task. But we should document the procedures and best practices behind those tasks.

Activity

  1. changed the title [-]Add a page for reviewing an interview for updates[/-] [+]Add a page or checklist for reviewing an interview for updates[/+] on Jun 26, 2024
  2. changed the title [-]Add a page or checklist for reviewing an interview for updates[/-] [+]Document procedures for reviewing an interview for updates[/+] on Oct 1, 2024
  3. changed the title [-]Document procedures for reviewing an interview for updates[/-] [+]Document procedures for reviewing an interview for maintenance/updates[/+] on Oct 1, 2024
  4. plocket commented on Apr 24, 2025

    @plocket
    Collaborator

    From this issue describing a post MVP task:

    ...do we have a current plan for adding navigation to existing interviews? As nice as it is, I don't think it's an urgent task. It's more of a recommendation for ongoing maintenance and improvements that we triage. The longest interviews already have it. It's a step on our maturity model. And this issue feels too vague to be a tracking issue.

    If we want to prioritize it, it needs to be more actionable first. E.g., with a list of the sections, a model interview, and instructions for a student to follow. We don't need the open issue here to know that having navigation is useful.

    This is inspiring me that maybe we need a "chore" type automated task that says "evaluate bringing this form to the next maturity level" that cycles through each form on a regular basis somehow.

    I personally dislike the name "chore" because of its connotations. Maybe "maturity"?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requeststarterGood first issue for DAL developers

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions