Brief summary of lessons learned about course information business processes in Manchester Metropolitan University's 4 year, JISC-funded Supporting Responsive Curricula project

1. CDD projects found “many problems with management of
course-related information … duplication of effort and of
information, lack of version control, poor re-use…”
Practice is too We struggle to QAA commend our
varied to interpret vague robust processes
systematise QA docs
Central systems don’t
Student Records QA We keep it vague to
support local variety so
avoid tortuous QA
We re-type we build our own
everything
into UCAS
We can’t get concrete
Marketing
details on courses for Course Teams Why do marketing
website, so maintain never have up-to-
our own date info about our
courses

2. So… engage stakeholders to find interventions that
will make a real difference
QA We review
hundreds
A robust way to ensure
modules demonstrate
constructive alignment
We set up We design next
thousands year while
A precise way to A simple way to
capture all next say how I intend delivering this
year’s module to assess learning
assessments outcomes
Student Records Course Teams

3. And … use the Tech to facilitate & accelerate
joined-up processes … MMU did!