I have spent time on the future phases of ServiceNow - meeting with the PMs, planning meetings with Fruition (the systems integrator), and setting up conversations next week with other parties so that we can begin scoping. It was good to hear that the first workshop day had been a success, and that while there is no slack in the project, the overall risk rating for our implementation is low - presumably due to lack of complexity in this initial phase. That sounds positive.
I also did some more work on developing the one page IT strategy into a format we can start working on here. There was some useful input to this later in the week from others who I shared the draft with. This will be an iterative process but also a "quick win" if we can agree the shape and content.
There were several conversations this week about none-teaching activity within WOLF. We need to ensure that the requirements that are emerging are really well understood - various people are digging into this area with gusto. There are potentially some other WOLF-related activities which are not currently being considered in scope, and as a result of our conversation today, I will develop a "landscape" (with others) to try and ensure that we uncover any other areas.
There were quite a few actions arising from the Leadership Team meeting and I will pick mine up during next week. The session was really positive and good to be talking about future planning, culture change and new Ways Of Working (WOW). There is a positive vibe around the place which is really good. This was reinforced by a number of "small successes" reported at the scrum meeting which took place for half an hour today. The Engineering and Science Faculty was present, which is also positive, and provided us with a potential cloud-based leave management solution which has been running successfully in the Faculty - and which deals with some of the harmonisation issues that are going to be tackled.
My time spent with the enquiry team was illuminating explaining the central enquiry team processes and data collection activity. Others in the sector are making investments in digital recruitment, but nevertheless we have some robust and automated processing largely based in one system. We have agreed some follow up actions about improving data input validation which would make a difference and is currently being tackled in different ways, in different places. Right now we don't appear to have postcode validation or email validation on any data input forms going into eVision (SITS). That should be fixable.
No comments:
Post a Comment