1 / 3

Common themes emerge from each of the ISGs:

PCG/10/15. Watching the ISGs in action and talking to the Chairs, there is a general questioning of the value of ISGs. Common themes emerge from each of the ISGs: What is the purpose of the ISG – are we just part of an administrative process ?

kyrene
Download Presentation

Common themes emerge from each of the ISGs:

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. PCG/10/15 Watching the ISGs in action and talking to the Chairs, there is a general questioning of the value of ISGs Common themes emerge from each of the ISGs: • What is the purpose of the ISG – are we just part of an administrative process ? • Are we toothless? How to make this more than a discussion forum? If it was there to prioritise expenditure then it would be worth it. • How do we keep the college representatives engaged and interested to come? • There is too much paperwork • Are we duplicating the work of project boards? • Does everyone read it - It is clear from the meeting who reads the paperwork beforehand The challenge is to enable ISGs to have ownership and accountability for managing the portfolio of systems development within their areas

  2. Each ISG is the guardian of system requirements for their given area of the University The ISG is the where IT and its customers interface. It has a strategic and an operational role in ensuring the right projects get initiated Business needs (defined in strategies) Understanding the need Once a year (in Sep??) the ISG asks these questions in order to refresh their view of the systems landscape in their area. This sets the context for systems discussion throughout the year What systems do we have v need to enhance v need to develop/buy to support these needs? What needs do we address now v later For those project we want to do now Discussions (Proving input to help colleagues shape up ideas) Satisfying the need For the rest of the year the ISG supports the initiation of projects that fill the gaps in the systems landscape Review proposals and PIDS (Is it fit for purpose?) Review our current portfolio of live projects (Are there any in trouble that need our help) The ISG is the where IT and its customers interface. It has a strategic and an operational role

  3. What does this mean for the way that ISGs operate? • Once a year (Sep) the ISG meeting focuses on reviewing its system landscape and agreeing what projects should be seen as a priority for the year • During the other meetings: • There are discussions about new ideas. The ISG can express its support or otherwise for the work depending on how far it satisfies the agreed priorities for systems development. • Proposals and PIDs are reviewed in a structured way to gain approval ie there is a list of fit for purpose criteria by which a Proposal/PID is assessed during the meeting. These might be: • Is the scope clear? • Are there defined deliverables? • Does the budget look complete and sensible? • Are there resources nominated and do they look appropriate (right people/right quantity)? • There is a dashboard of the current projects within the ISG portfolio. Projects that are red submit a report outlining what the issue is and either how they are addressing it or what help they would like from the ISG to solve the issue. Only these projects are discussed at the meeting. This is new We do some of this already but just need to make it a bit more focused and formal

More Related