Submitted by Jennie Franke
Enterprise Applications (EA)is rolling out “Change Tiers” to provide a framework to our teams guiding process and documentation rigor that is required to support our diverse portfolio of applications-departmental, administrative and enterprise.
Step 1: Evaluate the Risk
For Enterprise Applications, the risk of a change is a combination of complexity and impact. We’ve encountered times when a simple, straightforward data change has broken payroll (resulting in a large impact for the university). And a complex autosys job change might have little impact if it failed (i.e. it could be manually run). Based on this, the teams will evaluate each change with questions like:
Step 2: Identify the Tier
Based on the risk evaluation, each team will identify which tier applies:
*EA supports some systems and integrations that allow the business group to make changes. These changes fall outside our control and so have been identified as a separate tier.
**Tier 1 is only for systems with an online application for changes. Lessons learned in EA have lead us to conclude that only these systems are truly low complexity for our department.
NOTE: Because of the scope of systems we support and the intricacies of the integrations it was challenging to create an EA-wide guide for how to apply the tiers. Each team will create their own guide on how the tiers apply to their portfolio of applications.
- Request for work-Requirements
- Design-System Test Plan/Scripts
- User Test Plan/Scripts
- User Authorization
- Implementation Checklist