Portfolios and services
|
|
Prioritisation of IT projects
After a project is proposed the IT project team will prioritise the project as either; critical, high or low priority. The definitions and how we determine what fits into these categories is outlined below:
Critical
- has aims that are referred to in the faculty strategic plan or any other strategic documentation (i.e. a strategic plan for technology
within the faculty etc)
- a project that the faculty will rely heavily upon and has no temporary
replacement or 'work around' before the project has been completed
- has faculty wide implications (for all staff and students)
High priority
- is being delivered for the benefit of many in the faculty
- has many stakeholders/sponsors that want to be actively involved in
the project (the idea being that when stakeholders are active there is
more motivation and input and pressure and things tend to run more
smoothly)
- has a short time frame and a relatively large return
- has requirements easily met by the expertise or technologies already
found in the faculty
Low priority
- has a large time frame and a relatively small return
- is for only a small cohort in the faculty
- has stakeholders/sponsors that are not engaged in the project
- has requirements foreign to the technologies or skills set already
found in the faculty
|
