Skip to main content

Listening to users

At today’s meeting of the project board for the Office 365 for Students project, the main topic of debate was when to switch over from the old mail system to the new.  All the technical work is currently progressing well and we expect to be ready by the start of the new semester, so this shouldn’t be a constraint.  The issue is when would be most convenient for the student community.

The message from the school and student representatives on the board, backed by the User Support Division, is that we should wait until the new (calendar) year.  At the start of the academic year, students are focussing on settling into their new accommodation and their new courses.  For first years in particular, they will have more pressing concerns than a switch to an new e-mail system.  They will be using the student e-mail system already to receive important messages from the university and we don’t want to disturb this communication path.

The next option we considered was switching over in the middle of the semester, after students have settled in and before exams.  This could work but again the representatives felt that students would be too preoccupied with their academic work.  Also, if anything did go wrong in the switchover, this would impact their work directly.  We’re not expecting to see problems in the switchover but we do have to manage the risk.

So the preferred time is the first week in January, if possible.  This will be a quiet time for students, with plenty of time to tell them about the plans in advance.  We expect to switch to the new system in the week before the start of the semester, giving us enough time to sort out any minor problems before the students start using the system in earnest.

This shows the value of a project board.  As technically minded staff, the project team (myself included) would probably have pressed ahead and brought the service into operation as quickly as possible.  Instead, there will be a four month gap between finishing the build and actually starting the service.  This should give a better experience for the people who actually matter – our students.

Comments

Popular posts from this blog

2016 has been a good year

So much has happened over the last year with our Enterprise Architecture practice that it's hard to write a succinct summary.  For my day-to-day experience as enterprise architect, the biggest change is that I now have a team to work with.  This time last year, I was in the middle of a 12-month secondment to create the EA practice, working mainly on my own.  Now my post has been made permanent and I have recruited two members of staff to help meet the University's architectural needs.

I have spent a lot of the year meeting people, listening to their concerns and explaining how architecture can help them.  This communication remains vital, the absolute core of what we do and we will continue to meet people in this way.  We also talk to people in other Universities in order to learn from what they are doing and to share our own experience back.  A highlight in this regard was my trip to the USA last January.

Our biggest deliverable for the past year was the design of the data wa…

A new EA Repository

One of my goals since starting this job two years ago has always been to create a repository for architecture documents.  The idea is to have a central store where people can find information about the University's applications, data sources, business processes, and other architectural information.  This store will make it easier for us to explain our plans, to show the current state of the University's information systems, and to explain what Enterprise Architecture is all about.

It's taken a long time to reach this goal, mainly because we're often had more pressing and immediate work to be done.  The creation of a repository is one of those tasks that is very important but never quite urgent.  So I'm now very happy to say that we are in the process of deploying a repository and modelling tool.


This is the culmination of a careful process to select the most appropriate tool for our needs.  We began by organising several workshops to gather requirements from a rang…

New staff for the EA team

I'm delighted to welcome Jason Murphy, who joins us as our CRM Architect, and Wilbert Kraan, our new Data Architect.  Both Jason and Wilbert have worked as consultants for several years and bring new skills and considerable experience to IS.  They both know more than I do about their respective fields, which is how I like to hire people.

So the Enterprise Architecture practice now comprises the three of us, instead of me working on my won, which means we have more capacty to guide the University's IT architecture.  We can offer a greater range of skills and can bring a wider range of experience to bear.  I'm really excited about the opportunities this presents.

As his job title implies, Jason will focus on contact relationship management, working to build a user community and to create a strategy for managing and improving the University's relationships with prospective students, research partners, community organisations, and other parties - to give them all a better …