Halo - Delivery and Governance
Programme Delivery
Programme Delivery Methodology
We are using an Agile delivery methodology to allow for iterative development, continuous feedback, and the flexibility to meet evolving requirements. It ensures that we can align closely with the University's needs and objectives throughout its lifecycle. To start with, in the initial phases, there will be a focus on onboarding functions within the central university onto the new platform.
Programme Governance
Programme Board
The Programme board meet monthly to make sure the programme meets the University's needs and provides value. They report to the Information and Digital Committee (IDC) and work closely with the Portfolio Committees, other groups, and senior stakeholders.
| Programme Board Members | |||||
|---|---|---|---|---|---|
|
Liesl Elder, Development and Alumni Engagement |
Kirstine Knox, Development and Alumni Engagement |
Adrian Punaks, Development and Alumni Engagement |
Natasha Heaton, Halo |
Ricardo Goncalves, Halo |
|
|
Pascale Medioni, Halo |
Renee Duncan-Mestel, Halo |
Marco Zhang, Oriel College |
Tess McCormick, Mansfield College |
Eleanor Sansom, Blavatnik School of Government |
|
|
Kate Foley, Said Business School |
Antony Green, Development and Alumni Engagement |
Bethan Williams, Development and Alumni Engagement |
Holly Peterson, Development and Alumni Engagement |
Kate Lawton, Development and Alumni Engagement |
Strategic Readiness Board
The Halo Strategic Readiness Board exists to shape the future direction of the University’s CRM capabilities beyond the retirement of DARS. It is responsible for ensuring organisational readiness, defining strategic priorities, and embedding the structures, roles, and culture necessary for long-term success of the Halo platform.
A particular focus this Financial Year is to ensure we are ready to design and deliver the student lifecycle and the SRB will be considering such things as the order of the delivery of capabilities to ensure maximum value.
| Strategic Readiness Board Members | |||
|---|---|---|---|
|
John Ireland, IT Services |
Nadia Pollini, Graduate Admissions and Recruitment |
Rasheeda Azam, Undergraduate Admissions and Outreach |
Natasha Heaton, Halo |
|
Idonea Muggeridge, Undergraduate Admissions and Outreach |
Elaine Aitken, Student Systems, Education Portfolio |
Tiffany Ko, Continuing Education |
Ricardo Goncalves, Halo |
|
James Bristow, Assurance |
Amanda Tilley, Balliol College |
Haas Ezzet, Garden, Libraries and Museums |
Dave Smith, Enterprise Architect |
|
Brian Marsden, Medical Sciences Division |
James Mundey, Engagement and Dissemination Portfolio |
Elaine Aitken, Student Systems |
Phillip Camp IT Services/Humanities Division |
|
Liz O'Farrell, Technology Portfolio |
Rebecca (Bex) Roberts Halo |
Lowri Jones, Jesus College |
Lesa Levett, Medical Sciences Division |
|
Jeanette Sjoberg, Microsoft |
Mary Teeter, The Mathematical, Physical and Life Sciences Division |
Kate Davy, Graduate Admissions |
Tony Gooden, Microsoft |
|
David Plume, Finance Division |
Alan Ramsey, Halo |
Clive Wood, Microsoft |
Amanda Tilley, Balliol College |
|
Tom Trower, Undergraduate Admissions and Outreach |
|||
Architectural Review Board (ARB)
| Architectural Review Board (ARB) | |||
|---|---|---|---|
|
Saffron Greenwood, Infrastructure & Platform Services |
Robin Stevens, Information Security |
John Ireland, Interim Director of Software Solutions |
Richard McDonald, Solutions Architect |
|
Emma Hatfield, Halo |
Benjamin Hill, Enterprise and Integration Platform Manager |
Heidi Hunt, Student Registry |
Deb Sanders, Lead Data Architect |
|
Shirin Tahzib, Interim Chief Data Officer |
Dave Smith, Enterprise Architect |
Key Milestones
- Business Case Approval (October 24): Unanimous approval by Information and Digital Committee.
- Vendor selection (November 24): Microsoft selected as the preferred partner, in line with Oxford’s Microsoft first policy.
- Planning & Scoping (December 24): Agreed Statement of Work and stakeholder engagement began.
- Programme Approval (February 25): Approval from University Council
- Phase 1 Discovery (Hilary term 25): More than 20 workshops with colleagues to requirements.
- Early Adoption (2025): Initial system configuration by early adopter teams.
- Phase 2 Discovery (Trinity term 25): Colleagues from functions, divisions and departments participate in initial phase 2 workshops.
