ARIADNE-PM, is the ARIADNE methodology that supports primarily
organizations not developing technology since they have either limited
resources, know-how, and capability or the development process is not part of
the organizations operations plan.
Theses organizations do not have structured internal IT departments that
can support of fulfil development or even project management needs. They usually restrict the activities of their
IT professionals, if any, to support their users.
Other reasons than organizations might not have the capability of need to develop technology can be the following:
On the other hand these organizations want to be able to manage
successfully the information technology projects that they acquire when they
decide. Project management to theses organizations
is like investment management. Time,
budget and quality are very important factors and need to be assured in every
project. Such goals can only be obtained
if the following processes are executed and manage correctly:
The ARIADNE-PM Methodology helps an organization manage successfully all
the above issues under a very large number of project and organizational
constraints.
ARIADNE-PM, is composed out of the following twenty (20) phases for the project management and project acquisition management effort in information technology projects.
There is no technical description of each phases of the ARIADNE-PM Methodology
at this document, since this is a brief presentation of the entire
methodological concept of ARIADNE.
Technical documentation of each phase is available on other
publications.
The following figure presents the
conceptual structure of the ARIADNE-PM Methodology and the process of using the
methodology phases, based on dependencies, during the management of a project.