Skip to main content

The name of the game is… partnership.


The next talk was by Simon Walker of the University of Greenwich.  Simon gave several examples of how the Greenwich Connect programme is attempting to use IT to transform teaching and learning.  Some of the ideas are ones I’ve heard elsewhere, such as flipping classrooms, lecture capture, Box of Broadcasts, etc.  Others were new to me. 

For example, Greenwich give an ipad to each of their science students, to replace the traditional lab book and to allow common apps.  One academic worked with a developer to produce an app that can display the screens of all the ipads in a tutorial group in a grid on the classroom’s screen so that the tutor and the class can compare everyone’s work.

Greenwich Connect recognises that personal networks are a key part of how people find jobs.  Some of their students begin University without such networks and leave without developing them.  Simon suggested that an emphasis on collaborative learning and social media can encourage people to form better networks.   But increased use of social media can bring its own challenges and training requirements. What should a tutor do if a student tweets or posts that they’re unhappy and want to kill themselves?  The institution needs a policy backed up with training and support for staff.
Greenwich Connect came with very strong governance to make it work.  The initiative created working groups on social media, VLE, distance learning, and mobile technology, each chaired by an academic.  These all reported to a steering group. 

There were more ideas in Simon’s talk than I can capture here.  One that stood out for me was that if you type /research into a browser, you get a page full of glittering examples. What happens if you type /learning or /teaching?  Often nothing.  (Edinburgh has www.ed.ac.uk/studying, which is close, but the two examples that Simon gave don’t yield results).

Comments

Popular posts from this blog

Presentation: Putting IT all together

This is a presentation I gave to an audience of University staff: 

In this seminar, I invite you to consider what the University’s online services would be like, if we worked together to design them from the perspective of the student or member of staff who will use them, instead of designing them around the organisational units that provide them. I’ll start with how the services might appear to that student or member of staff, then work back from there to show what this implies for how we work, how we manage our data, and how we integrate our IT systems. It might even lead to changes in our organisational structure.

Our online services make a vital and valued contribution to the work of our students and staff. I argue that with better integration, more consistent user interfaces, and shared data, this contribution could be significantly enhanced.

This practice is called “Enterprise Architecture”. I’ll describe how it consults multiple organisational units and defines a framework …

Not so simple...

A common approach to explaining the benefits of Enterprise Architecture is to draw two diagrams: one that shows a complicated mess of interconnections, and one that shows a nicely layered set of blocks. Something like this one, which came from some consultants:


I've never felt entirely happy with this approach.  Yes, we do want to remove as much of the needless complexity and ad-hoc design that litters the existing architecture.  Yes, we do want to simplify the architecture and make it more consistent and intelligible.  But the simplicity of the block diagram shown here is unobtainable in the vast majority of real enterprises.  We have a mixture of in-house development and different third-party systems, some hosted in-house, some on cloud infrastructure and some accessed as software-as-a-service.  For all the talk of standards, vendors use different authentication systems, different integration systems, and different user interfaces.

So the simple block diagram is, basically, a l…

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…