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 ?
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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Common themes emerge from each of the ISGs:
The challenge is to enable ISGs to have ownership and accountability for managing the portfolio of systems development within their areas
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
(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
This is new
We do some of this already but just need to make it a bit more focused and formal