Aggie Enterprise Planning application enhancement request process
The Aggie Enterprise Planning application is continually evolving, and ideas for enhancements that improve functionality and user experience are welcome. The enhancement request process involves different stakeholders but is straightforward. The following diagram summarizes the overall steps in the enhancement request process.
Note: Unit leadership (Senior Analyst or Assistant Dean/Chief Operating Officer role) must either submit or be copied on Help Desk tickets. Because unit leadership is expected to evaluate all department requests, Planners should consult with them before the tickets are submitted.
For the detailed description of the steps, expand the following sections.
- Step 1 - Submit an Aggie Enterprise Help Desk ticket.
User responsible: Planners or unit leadership
Either Planners or unit leadership can submit the Help Desk ticket. If Planners submit the ticket, unit leaders must be copied and will be expected to indicate whether they approve the request. Planners should consult with unit leadership before the ticket is submitted.
When completing the ticket, be sure to include the following information:
- Description of the request
- Justification for the request (including business need, efficiency gains, new compliance requirements, and so on)
- Indication of approval from unit leadership
- Relevant details of examples to provide context
- Screen mockups that illustrate the concept, if possible
- Step 2 - Review request for feasibility and level of effort.
User responsible: BIA and Planning Business Systems Analyst
During the review, the team might contact the requester for clarification or additional information.
- Step 3 - Present the request to the Aggie Enterprise Planning Change Control Board (CCB) for review and approval.
User responsible: Requester or delegate
Requests that require 8 or more hours of effort or have high impact are routed to the CCB for review.
Requests that require less than 8 hours of effort are reviewed and may be approved by BIA without CCB review.
- Step 4 - Develop and release the enhancement.
User responsible: Planning Business Systems Analyst and Requester (or delegate)
Approved enhancement requests follow the standard software development life cycle, which includes development, testing, validation, and controlled migration to production. Status of the approved requests are published on the Known Issues and Approved Change Requests web page. You can check the web page to track approved requests.
Enhancement requesters are responsible for acceptance testing, which is the last phase of software testing before the enhancement is released.