PROD Development Workflow

Goal

What is the process?

1. A ticket is automatically created by Triage within Customer Request (CR) process

   1. Ticket is automatically filtered within Backlog or Prioritized based on CAT

   2. Ticket will show up on appropriate Kanban based on Team assignment

2. Pick up the ticket at the top of the Prioritized column

   1. Product will be maintaining this column

3. Assign yourself to the ticket

4. Begin work to diagnose and resolve the issue

5. Tag Leads if you believe the issue will take more than a week to complete

   1. This will allow expectations of stakeholders to be set appropriately and prioritization to be clear
6. Tag Leads with status/questions/concerns as needed

FAQ

What if the ticket does not provide enough data to complete?

• Move the ticket to Waiting on Reporter

  • This will manually update the status on the CR ticket

• Add the question or request to the CR ticket directly

  • Non-engineering discussion should be limited to the CR ticket

What if the Platform Area/Team from CR turned out to be wrong?

• Feel free to correct that data as it will help with reporting
• Platform Areas & Product Components: Full Listing

What if this issue relates to active development work?

• Follow necessary triage steps in: edX Active Feature Development Work & Ownership