​IT Projects vs Requests

Information Technology separates work into three categories: Projects, Requests, and Operations.

A Project is defined by the Project Management Institute as "a temporary endeavor undertaken to create a unique product, service, or result." Projects require more work than requests and are typically done to implement a new service or make significant changes to an existing service. For project examples, please see the IT Project Roadmap.

The difference between small projects and large requests is not always clear. When in doubt, please contact the IT Project Management Office to discuss your needs. ​​

All proposed projects must be approved by the IT Project Review Committee before beginning planning or execution.

See the UWSP ​Definition of an IT Project section below for more details.

Requests are smaller in nature than projects. They are typically less complicated, require less effort, and often follow pre-set processes. Requests are often submitted as tickets or work orders. Examples of requests are the purchase and installation of supported hardware, installation of software, or support of an existing service which may include issues or minor modifications.

Operations work is routine, ongoing work done internally by IT in support of UWSP's existing services and infrastructure. Operations work is not directly requested by groups outside of IT but sometimes may be the result of a request. Examples include the maintenance of the campus network and server infrastructure, the packaging and release of OS and software updates, and hardware lifecycle management.

UWSP Definition of an IT Project

An IT project typically performs the following functions and meets the criteria as listed below. Additionally, projects are not ongoing or repeating and instead are completed and delivered within a specific timeframe (see Projects and Operations above).

Function (1 or more)

  • Implement a new IT system, service, or process (including cloud services).
  • Make significant improvements or upgrades to existing IT systems, services, processes, hardware, or software (including cloud services).
  • Research new technology for a specific purpose.

Criteria (2 or more) 

  • Requires more than one week (40 hours) of IT effort.
  • Involves significant effort from multiple departments within IT.
  • Involves procurement of unique or complex IT hardware, software, or cloud services.
  • Requires significant documentation, training, or communication.
  • Has significant impact on multiple areas.
  • Has a difficult to understand problem or complex solution.
  • Has a high level of task interdependency, or complex relations with other projects or existing campus services.
  • Must be delivered within a specific timeframe.
  • Has significant interest or involvement of campus leadership.

​​​​​​