Project and software implementation

A project is a unique process composed of many coordinated and controlled activities with dates of initiation and completion, performed to achieve a goal which suits specific requirements, including limitations given by time, costs and resources.

It can be realized for new or existing customers. It controls and checks the agreed processes, time schedule and actively cooperates with the customer with the goal to fulfill the Contract with the customer within the agreed deadlines. It is responsible for meeting the economical and time goals of the project.

A project has the following characteristic features:

• goal – product / service and their functionality / parameters
• Quality with which the goal should be realized (metrics)
• Sources used to fulfill the goal
• Deadline by which the product must be submitted
• Costs – i.e. budget which will be withdrawn
• Risks, how to avoid them during the preparation of the procedures or what to do if they occur
• Limits which will influence the project

There is no worse situation for the supplier of a product or service, than an insufficiently defined goal – product, which should be supplied. Quality documentation should be an important matter of course. If the supplied product is not satisfactory at the end of the project, it is really to late to start to re-work or complete functions (besides minor adjustments which are, of course, on the other hand, usual) The supplier then has no other protection than the document – contract, in which he pledges what and with what quality he willl supply for the agreed price. At the same time, he should not conclude a contract which does not unambiguously specify this, because if he fulfills only an unspecific and incorrect assignment and the client is not satisfied, he risks, at the very least, his reputation.

The implementation itself is performed based on a pre-defined project. Its goal is to deliver products or service within the scope defined in the attached Project.