The purpose of this topic is to illustrate the eVoucher MR process. Through the MR process, eVoucher users provide the eVoucher Project with suggestions for improvements and other desired changes. While the process does adhere to the AO software modification request procedures applied to all nationally maintained applications, the eVoucher process is unique in that it also incorporates the assistance of an MR Task Force to prioritize and analyze modification requests. The MR Task Force is made up of subject matter experts and judges from various stakeholder groups, including District Courts and Courts of Appeals, Defenders Services Office, JIFMS/Department of Administrative Services. Data Governance, Security, etc.
The eVoucher MR process is outlined below. MR's may only be submitted by judges, court staff, and defender services staff. Attorneys and service providers with suggestions for modifications to eVoucher should contact their local court and or federal defender services office.
▪ Step |
▪ Action |
▪ Description |
1 |
MR submitted by end-user. |
MR’s are submitted electronically. The submission of an MR typically comes at the recommendation of SDSO Support after they determine the issue can be replicated and validated, and cannot be resolved. SDSO also check to make sure the new MR and has not been submitted as a prior MR. If an MR was previously submitted, submitter will be advised that courts can add their support to the existing MR.*
*MR support from courts is encouraged and is considered greatly in the prioritization process for implementation consideration. |
2 |
Product Owners notified of MR entry. |
Product Owners review MR’s prior to validation by SDSO. |
3 |
MR is validated by SDSO Support. |
Once SDSO Support validates the MR by reproducing the issue and entering it into the MR database, the submitter will be notified.
The Product Owners work with SDSO Support to review and filter the MR list to determine if MR’s should be accepted and pushed to JIRA (or not), or to be accepted but closed right away.
MR’s with policy and other implications are sent to the eVoucher Working Group for input prior to the implementation decision. |
4 |
eVoucher Working Group analyzes and prioritizes list of MR’s. |
The eVoucher Working Group meets periodically to evaluate, prioritize, and recommend MRs for implementation by assessing the value of MRs to the Judiciary as a whole. |
5 |
Approved MR’s slated for development by Product Owners. |
Approved MR’s will either be incorporated into the eVoucher development backlog using the priorities provided and slated for development along with other needed functionality, or assigned to provide specific training information so that users understand how to use the functionality to get desired behavior. |
6 |
MR database updated. |
SDSO Support updates the MR database with the status of the MR’s. Those that will be implemented will indicate the assigned release. Originating courts are notified of the status of their submitted MR’s. |