Anticlue

Requests for Work.

There are multiple types of projects with various sizes. So lets start with one that doesn't need a charter, a detailed requirements process. I'm going to refer to these as requests. So how does one determine a request for work from the IT department vs a small project.

I think it is best to define requests by what they are, not by the workload associated with them.

First requests are for routine updates to keep system tables in synchronization. Have a doctor, need to have IS update all the system tables, that's a data request. Have a new employee, want to get him added to the 15 systems with appropriate security access, request. Want a report, write a request.

Second requests are not implementing new things. Implementing a new technology, system, or interface shouldn't be a request, it should be a project.

However, if you have the basic system in place, and an upgrade comes along. That is a request, unless the upgrade calls for a hardware refresh (project).

Normally the risk for requests is low, and only affecting one department.