Agile methodologies are quite common these days, but I can’t find a lot of documentation about which indicators are most useful and why. I found many more things saying that some traditional indicators, such as LOC and test code coverage, are not suitable, leaving two main questions:
Even with the Agile process, would you like to know how much code coverage you have with your unit tests? Or is it just that this metric (and others) is simply not as useful as other metrics such as cyclic complexity and speed?
Agile is a business-oriented thing; Agile is maximizing customer value while minimizing waste to ensure optimal ROI . This is what needs to be measured. And for this I use the system that Mary Poppendieck recommends . This system is based on three holistic dimensions that should be taken as a package:
, , , , .., - , . , , , ( " " "" ), .
, , .S. , :
, , :
, .
1.1) LOC
, ! JAVA Ruby,
, !
1.2)
, , , .
, , , . , , ! , .
2) (1) , , , , :
: , , , , .
: , ()
InfoQ . .
1, , Agile-.
LOC . , . , , , , .
( ) , .
2, :
LOC :
Agile , (. Agile Manifesto). . , , Agile-.
, , - . : http://xprogramming.com/articles/jatrtsmetric/
...
LOC - , , , : , , : , try-catch ... , , "" , - ..
, , , , , ( , !), , .
, , , ... LOC , , ... , , , !
, , , , , , , ... :
: dojos, , , , / , / ..
, , , , , , , - , ! , , . - , , .....