Page Comparison

...

TI3 Deliverables:

• Moodle 4.UX - UI/UX review of Titus Theme  - Image RemovedCTP-1801: Moodle 4.UX - UI/UX review of Titus Theme

  • What: Review the global approach to Moodle redesign - Not just theme, but to include course formats, navigation etc. Focused feedback UX interviews with stakeholder groups. Common task workshops. Identify issues and note comments—feedback into Titus design process.

  • Why: To ensure that the new Moodle Theme and combination of Moodle course formats and UCL System designer give our end user the best UI/UX experience we will be working with a Moodle specialist UI/UX to provide an "informed" point of view of our development and advise us on any additional changes we should implement to the UCL Moodle. We will also use this opportunity to document the license under which we are engaged with Titus learning in providing the UCL "leased theme" to ensure we understand what changes UCL can make to the Theme either directly via Titus or via UCL staff or another 3rd party.

  • Dependency: ? / Risk: ?

• Moodle 4.2 - UX - MyFeedback rework - Image RemovedCTP-1992: Moodle 4.2 - UX - MyFeedback rework

  • What: Scope out UI/UX  development work for an improved MyFeedback. Produce wireframe/mockups. Agree mockups. Identify development partner. Develop UI/UX. Iterative feedback cycle on development. Agree release MVP. Release and Deploy as part of Moodle 4.x. Update Documentation. Communicate change.

  • Why: Review UCL MyFeedback report plugin to improve user experience. From work identified in the 4.UI/UX, we will rework the UCl MyFeedback UI/UX to work with the new Moodle Theme and improve its overall accessibility and user experience.

  • Dependency: ? / Risk: ?

• Block development - Image RemovedCTP-2045: Block development

  • What: Development for UCL’s dashboard. Blocks include marketing block, site announcements, and feedback.

  • Why: ???.

  • Dependency: ???.

• Moodle 4.UX Titus Development of new UCL Theme - Image RemovedCTP-1791: Moodle 4.UX Titus Development of new UCL Theme

  • What: Design of new Moodle theme. Clear agreement and terms of use for the Titus theme. 
    Engagement with Titus learning to ensure Theme matches UCL desired expectations and requirements. Stakeholder feedback. Adherance to UCL Design-System. Deployment of preview instances.

  • Why: As a user of Moodle 4.x I will have an excellent user experience in look, feel, navigation and over all use of the Moodle 4.x platform. As a senior stakeholder UCL Moodle will look “modern” “high quality” “premium” and match the insitutions reputation for excellence. As a member of UCL Digital Presence the UCL theme will adhere to the UCL banding and system design as much as is possible within the Moodle application.

  • Dependency: ???.

• Development of the new UCL Theme by Titus Learning - Image RemovedTCTP-1990: Development of the new UCL Theme by Titus Learning

• • What: Design discussions between UCL and Titus to continue to refine UCL requirements and deliverables. To actively seek feedback upon the theme development via engagement with stakeholder groups. Timely responsive and relevant communication to be delivered to appropriate stakeholder groups e.g Blogs, Townhalls, staff news etc
    • Senior stakleholders
    • User focus groups
    • Moodle Development User group
    • Digital Accessibility team
    • UCl Design team
    • General staff and student

...

Why: Engage with both focus groups and wider community. Ensure clear and appropriate communication with stakeholder groups. Obtain feedback feed into continuous improvement process. Make selected themes available to Digi-Ed staff and to wider user group to elicit feedback. This should be staged with user group expanding as choices narrow on theme design.

• Outcome Description:  

  • FOR WHO: Staff and students

  • WHAT: Core UCL service data integrations and interactions with Moodle. Such as SITS/Moodle, CMIS/Moodle, Lecturecast/Moodle Moodle/data repository/lake. Also, includes maintenance, support and continuous improvement activity on UCL-developed/maintained integrations such as the Course Life Cycle Toolset, Moodle Integration Manager (MIM) and MyFeedback.

  • WHY (Business Value): To provide a single source of truth data connections, reduce staff time in manual tasks, improve data consistency, alignment with the data strategy, requested and required functionality, automation of manual tasks and the continued support maintenance of UCL developed tools.

• Dependencies / Risks:

  • Specific integration developer knowledge (D/R)

  • Other UCL core services and their product teams (D)

• Outcome Deliverables EPICs:

TI1

• Create Mockups for Assessment Wizard (Spike) https://ucldata.atlassian.net/browse/CTP-2513 - Jason

  • What: https://ucldata.atlassian.net/browse/CTP-2494

  • Why:

  • Dependency: / Risk:

• PILOT - Moodle/Sits Integration - Grades - https://ucldata.atlassian.net/browse/CTP-2648 / https://ucldata.atlassian.net/browse/CTP-2351

  • What: Gather user feedback on the feature set; prioritised list of the features/functionality; go / no-go decision on MVP release; implement top priorities (ref: assessment wizard (epic) );

  • Why: Integration between the LMS and UCL’s SRS system is fundamental to providing better, faster and more efficient services to our stakeholder groups. Grade transfer is one of the core sets of integrations that will significantly transform operational activities. and reduce the burden on course administrators and tutors responsible for the transfer of grades to SITS. Grade transfer will also enforce SRS workflow processes and will increase data integrity. Grade transfer will also work to validate UCL Moodle as an assessment platform where summertime assessments take place. Grade transfer will also complete the grading loop for external products that may be integrated with Moodle such as Crowdmark.

  • Dependency: SRS / Risk: Developer resource, development timeline, limited MVP capability impacting stakeholder experience and view

• Course Life Cycle re-work - https://ucldata.atlassian.net/browse/CTP-2652

  • What: The Course Life Cycle tool introduced in 2022 has a large number of backlog items that need to be reviewed, prioritised and worked through (focus on improvements on the existing courses).

  • Why: The CLC backlog contains user enhancements, bug fixes and overall improvements to the tool. Early life for the CLC was not supported long enough due to other work pressures. CLC needs to be revised and improved to ensure user experience is where it should be.

  • Dependency: Resource / Risk: Stakeholder opinion on CLC decreases as issues and reported feature improvements are not acted upon

• Lectruecast rollover spike - https://ucldata.atlassian.net/browse/CTP-2650 UNCOMMITTED from Media

  • What: Lecturecast current LTI plugin does not facilitate any form of course rollover within Moodle, creating a large amount of work for course teams who need to remove old content and connect new Lecturecast sections every year. Discuss with Media Product the Moodle/Lecturecast if there are any possible solutions. Gather a requirements document, resource requirements and estimation of time and cost.

  • Why: The task of Lecturecast role-overs is a significantly negative experience for course administrators. The current manual method takes significant time and has been highlighted in multiple feedback loops by stakeholders as being a problem area.

  • Dependency: Media Product / Risk: Increased dissatisfaction with course roll-over activity