Making the Grade with Agile Transformation in Higher Education
summary
University College London reorganizes IT into 40 standing teams across eight portfolios, replaces project funding with long‑term product funding, and makes data visible in Jira so portfolio owners (like registrars and CPOs) decide priorities. A recruitment MVP drops time‑to‑hire from 127→48 days. An “inside UCL” UX layer decouples experience from a monolithic ERP, ships small increments, runs an automated test pack in a couple of hours, and steadily shifts culture from control to empowered product teams.
AI-written summary · about
chapters (14)
- 0:00Agile in higher education
- 1:06About UCL and speaker
- 3:13Traditional IT challenges
- 4:58UCL’s strategic goals
- 5:40How the pandemic accelerated transformation
- 6:22Four Agile shifts
- 7:47Empowering teams
- 9:12Five pillars of Agile
- 10:35Transparent data ownership
- 11:58Role changes and learning
- 12:39Faster recruitment hiring
- 15:06HR systems improvement
- 16:51Declarations of interest
- 18:38Expanding Agile adoption
related talks
31mThe Unilever DevOps Journey So Far: Finding the Speed to Innovate
44mCan you be agile and compliant?
48mTurning the ship or the lighthouse
18mManaging Change
35mBuilding and Growing an Agile Team
40mMoving from the License Raj to Light Touch Agile Governance
43mWhy Agile transformation fail
18mAgile leadership and technical mastery, a harmonious alliance