that firms may find themselves juggling the resources required to manage not just one, but many projects
focused on technological innovations. Both of these factors certainly create an exciting, yet stressful,
environment for both the businesses involved, as well the project teams that do the work.
A second feature associated with IT projects is the difficulty encountered by human resource personnel
charged with hiring and retaining experienced IT project employees. In other words, not only may
technologies change during projects, but a project team may also experience a certain level of turnover as
valued employees seek new opportunities. This is made even more challenging by the fact that the
demand for employees with good IT project experience may be particularly high, thus companies may
need to design lucrative compensation packages to prevent the recruitment of these employees by other
organizations.
A third feature is the need to manage the extensive amount of user involvement necessary in information
technology projects. Unlike many other types of projects, an information system may be replicated across
different parts of an organization, possibly in different parts of the world. As a result, particular
attention needs to be focused on each subset of potential users as the system is built. In addition, a
project development team must also be aware that an information system is likely to be used by people
with very different levels of technical proficiency. As a result, many different types of users need to be
involved in the development process to ensure system success. Systems designers charged with the
development of an IT system must ensure that the end users of the system are involved throughout the
project. This includes involvement not only during planning, but also during both implementation and
maintenance.
A fourth feature involves the need to understand established systems development methodologies and
how these can be integrated into a project management framework. There are literally dozens of
published methodologies for developing and maintaining systems available to organizations and project
teams. These methodologies may be similar to the traditional systems development life cycle (SDLC), or
closely aligned with rapid application development (RAD) and/or prototyping. In any event,
understanding how these methodologies relate to the standard techniques available in the project
management domain is a unique aspect of managing information technology related development
efforts.
A fifth feature that may distinguish an IT project from many other types of projects is that the solutions
that are being attempted may never have been done before. Whereas building a new house is certainly a
project, it is a project that is likely very similar to past projects your general contractor has attempted. IT
projects, and the other hand, may be focused on building a system that has entirely new functionality. In
such a case, there may be few guidelines or past lessons learned for the project team to rely on.
A sixth feature relates to scope management. While project scope¹which relates to the planned definition
and size of a project¹is likely to change in many projects, in many cases a progressive, uncontrolled
increase in project scope is commonplace in many IT projects. In many instances, this may relate to the
fact that the product being produced may have never been developed before, as mentioned in the
paragraph above. In such a situation, users may be less definite on what characteristics they want in the
final project output. In addition, users may naively believe that software projects are easily modified
even after they have began¹after all, it is just changing a few lines of code.
The seventh unique feature of IT projects is that the technologies involved in projects may change during
the project itself, presenting a moving target for a project team. As an example, a company may be
involved in the deployment of an Enterprise System, such as SAP, for the purpose of connecting various
functional areas of the business, such as production, sales, and accounting. During the middle of such a
project, a new version of the system may be released, and the company may find itself faced with a
decision regarding whether or not to continue on with the original product, or adopt the new technology.
Such changes in technology are commonplace, adding to the complexity of managing projects of this
nature. In some cases, this may result in the technology becoming obsolete before a project is even