Skip to Main Content
When the initial requirements of a software project are not so consolidated and there is a gap from what the user is able to express and what actually is needed, it seems obvious that the traditional way of "waterfall" developing approach is not so much recommended. The Agile approach (based on iterative-incremental model) mitigates the possible risks by classical way of software development cycle proposing instead of "doing once for all", "a piece by piece" model, developing the software through a sort of "try & verify" incremental approach. In today complex context, where continues changing needs and hence instable requirements are present, adopting agile project organization approach is getting more and more frequent offering positive feedback results. What is going to be discussed in this paper can be seen through two parts. At first, there will be a short description of GQM & PSM methodologies, focused on selecting a number of "sensible" metrics in Agile based software development context, while the second part will be concentrated on the fuzzy set theory, fuzzy logic (with the associated rule based reasoning model) and their implementation on the selected metrics in order to evaluate & monitor a general agile based software development project.