To better support the implementation of new projects at University of Dallas, the Information Systems team has created a Project Request process. The project request process will ensure proper tracking of requested projects, approved projects, and in progress projects. The Information Systems team will be utilizing suitable project management techniques to assure defined projects are being delivered based upon resource availability, identifying critical tasks, mapping out logical sequence of task completion, avoiding scope creep, keeping the project on track for delivery, identification of communication plans and training needs, and capturing lessons learned to be used in future projects. The project request and implementation process will continue to be evolved to maximize transparency, collaboration, and teamwork across all University of Dallas' Information Systems projects.
Most projects consist of a number of steps. A project is temporary in that it has a defined beginning and end in time. A project is unique in that it is not routine operations, but specific set of tasks designed to accomplish a singular goal.
Examples of Projects:
A support ticket should be entered for routine operational support. Operational support tickets is a generalized term and refers to work performed by Information Technology teams. Typically support tickets are created to interact and track end user support issues.
Examples of a Support Ticket:
At the bottom of this page click the orange "Submit a Information Systems Project Request" button. You will be redirected to a Qualtrics form. Questions 1-9 are required to be answered. Question 10 is optional to submit related project documentation. Once submitted the Information Systems team will review.
Question number 4, 5, and 6 have minimum character counts to carry out detailed information needed to initiate the project. More information provided when submitting the project request form allows the Information Systems team to identify proper project resources, end user expectations, and proper planning to implement the project on time.
The organizational change question is a multi-select question. The purpose of the question is to assist with change management processing and organizational communication and training needs for the project and the end result when the project "go's live".
The initiation phase is setting the foundation for later success of the project. During this phase of the project there will be identification of need or problem that the project will solve. Secondly, the information systems team will be able to identify if the project is feasible and will solve the problem.
A project sponsor has a demonstrated interest in the outcome of the project and responsible for securing spending authority and resources for the project. The project sponsor initiates the project request process, is the decision maker for the project, supports the project manager, approves deliverable, and signs off on approvals to proceed in each project phase.
A project stakeholder can be a individual, group, or organization that may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project. Project stakeholders can be internal or external in nature. Not all stakeholders will come into play during a project life-cycle, but identifying them early can assist with project buy-in and expectation setting. Stakeholders will vary with each project that is being requested. You might consider the following examples of a project stakeholder:
University of Dallas Project Report
|The Project Report identifies current project that have been requested by requester, department, anticipated start and end dates. The report also identifies project changes, project complexity, and how the project supports the University of Dallas strategic initiatives.|
Have a Project? Submit a Project Request!