Open AccessProject Evaluation - Setting the Problem
Author(s) -
Andreas Munk-Madsen
Publication year - 1986
Publication title -
daimi pb
Language(s) - English
Resource type - Journals
eISSN - 2245-9316
pISSN - 0105-8517
DOI - 10.7146/dpb.v15i216.7567
Subject(s) - project planning , computer science , project management triangle , plan (archaeology) , project plan , task (project management) , project management , set (abstract data type) , work breakdown structure , project charter , software project management , management science , operations research , engineering management , process management , systems engineering , engineering , software , software system , business , procurement , software construction , archaeology , marketing , history , programming language
Evaluation of a system development project denotes those activities which aim at improving the understanding of the project and its environment. This understanding forms the basis for planning and regulating the course of the project. Project evaluation often takes place in a project situation which only deviates slightly from the plan. The project is then evaluated merely to determine the extent and consequences of the deviations. There are situations however, where the system developers know that something is wrong in the project. But maybe they cannot identify the problem, or they disagree on what the problem is. The task is to set the problem. This paper discusses how project evaluation can be performed in situations like that. It discusses guidelines for defining problems, and claims that a problem should be formulated as a contradiction. Project graphs and problem networks are introduced as description tools in project planning and project evaluation, respectively.