RISK

S Legacy systems could ‘feed’ into the new Programmes Plantbut might soon be replaced and could present data transfer problems

Publishing Office

Qua

lity Assurance

Depar

tmen

ts &

Schools

Enro

lmen

t Management Services

Student Data Systems

Implementation Group

Steering Group

Stakeholders were identi�ed representing all points at which course data was created, maintained, processed or consumed. Knowledge of current systems was shared and points of failure and con�ict and duplicationidenti�ed.

RISK

S Balancing the need to include all stakeholders against the need to keep working groups to a manageable size. Requirements for attendance tailored to agendas.

RISK

S Acknowledging errors with systems or systems ‘past sell-by dates’ whilst appreciating valuable contributionsfrom staff - the need for diplomacy

RISK

S Ensuring the product owner is supported by line managerand line manager is aware of the amount of time the product owner will need to give to the project

???wordswords

Project Manager

DevelopersDevelopers assess requirements with Product Owner. Revisit and learn from previous attempts to improve systems. Evaluate: bespoke v third party solutions enhance existing systems v new build.

RISK

S Avoiding scope creep whilst keeping all the stakeholderson board, interested and contributing (even though we maynot solve their problems within the life of the project)

the Kent XCRI Project

Product Owner

Links:

Existing methods for collecting data to feed the online course pages, data returns, subject lea�ets etc were not�t for purpose, prone to problems and reliant on a small number of dedicated sta�. The University lacked one authoratative source of data.L

esso

ns

Lea

rned

Wh

at

w

e d

id

Investigate current sources of course data - Where?, What?Who - owns? compiles? validates? administers? Weak points? Duplication? Anomalies? Inaccuracies?W

hat

w

e d

id

Set up the project administration. Appointed o�cers and recruited key people to advise, liaise and generally keep the project wheels turning, resolve con�icts and report on how we were doing

Wh

at

w

e d

idW

ha

t w

e d

id

There are a great number of people involved in the process of getting course data to the prospectivestudent. There are no clear hierarchies or paths in theprocess and no single point of authority

Les

son

s

L

earn

ed

People are busy & may not be able to contribute as much and as often as we would like

Le

sso

ns

Le

arn

ed

Product Owner acts as primary liaison between developers and users, reviews all developments, prioritises user stories and product features

Linking modules to Programmes on the course pages was key to improvingour on-line o�er

Less

ons

L

earn

ed

Change is hard - even when it is changefor the better. Keeping users informedand in the loop is very importantLe

sson

s

Le

arn

ed

http://blogs.kent.ac.uk/kent-xcri/ http://blogs.kent.ac.uk/webdev/http://www.kent.ac.uk/is/projects/xcri/https://github.com/unikent/programmes-plant

HEAR

KISprospects.ac.uk

etc.......

Wh

at

we

did Revised content, design & functionality

of online prospectus based on user needs

RISK

S Unpredicted events ‘bump’ developers off the project risking the project �nishing before critical applicationsare production ready

WHERE W

E STARTED

audrey

Product Owner

Developers

MinimumViableProduct

Product Owner

Developers

Development versions

Product Owner

Developers

Production version

the Programmes Plant

Our Goals

Developing a course data administration applicationand producing the XCRI-CAP open feed

XCRI