IT Project Request

Stop!    Before you submit a project request, please read the following:

How do I know if I have a project to submit? What doesn't count as a project?

  • Business-as-usual activities (BAU)
  • Low-effort ad-hoc requests
  • Services
  • Break/fix
  • Communication
  • Configuration (Low Level of Effort)
  • Software requests
  • Hardware requests

If your request falls under one of the above categories, please revisit the Client Services portal to find the appropriate ticket request.

What is a project?

A Project is a task undertaken to create, deliver, or implement a unique deliverable or other solution which has specific, agreed-upon constraints (including scope, resources, budget, and timeline). A project should have the following characteristics:

  • It is temporary in nature:
    • A definite start date.
    • A definite end date.
  • It has a defined scope:
    • The result to be achieved.
    • The work that must be done to meet that result.
    • Specifications about project goals, features, functions, tasks, deadlines, deliverables, and cost.
  • It has defined resources:
    • People, capital, and/or material goods that are required for the successful completion of the project.
    • It must be vetted and approved via the project intake process.

What do I need to submit a project request?

To submit a project request, you will need the following information:

  • Executive sponsor
  • Desired timeline
  • Description of the problem you're trying to solve
  • Business objectives
  • Any other information you can provide to help ITS understand the project. This can include...
    • Risks
    • Benefits
    • Business requirements
    • Other dependant projects
    • etc.

How does a project request become a project?

All submissions will go through the following process.

  • A project request will be reviewed to determine if your problem constitutes a project. If your submission is deemed not a project, we will provide you with the best path forward, which may include submitting a ticket to a different area.
  • Go through the Discovery process with the help of a Technical Business Analyst, you, and additional staff in ITS, depending on the project subject matter.
  • Added to the project processing workspace.
  • Categorized into the following:
    • Critical Service and Compliance Projects
    • Institutional Priorities (i.e. 2030 Strategic Plan)
    • Divisional / Departmental Strategic Goals
    • General and Non-Critical Service Projects
  • Prioritized based on the category (see above), timeline, risks, budget, and staffing.
 
Submit Project Request

Related Articles (1)

MSU Denver's definition of a project, as approved by the Steering Committee