The DLE’s change management process is based on this RIDE framework, where a DLE change request starts as a “Recommendation” (change request) and then Input is gathered from stakeholders and the DLE Advisory Council before going to the DLE Service Owner to Decide, and then on to Execution by the DLE Service Management team. If central funding is sought for the change, then the UWS Enterprise Directions Council (EDC) will be engaged in the process. Exceptions to the RIDE process include vendor-initiated changes that are generated through the product update cycle. This website is intended to support our institutions by providing easy access to DLE service-management information, documents, and forms used to support the management of changes in DLE technologies.
There are three main drivers for change within the DLE, as follows:
- Product Updates: Canvas, Kaltura, and Blackboard Collaborate Ultra make product updates though a “continuous-release” update cycle. The changes to the DLE occur on a frequent basis. Canvas, for example, releases monthly product updates for our users.
- UW System Stakeholders Change Requests: If there is a perceived gap in the DLE’s ability to meet teaching and learning needs, any UWS DLE user, including students, instructors, and administrators may submit a change request.
- UW System Stakeholders New Tool Requests: If UW System DLE users have identified an unmet teaching and learning need that could be met with a new third-party tool (i.e.,extra software not currently used within the DLE) any UWS DLE user, including students, instructors, and administrators, may request that a new tool be added using the “External Application Integration Request” process.
Regardless of what or who drives the change, each product update and change request is carefully evaluated primarily to ensure our security, data privacy, and accessibility requirements are met.