Software development effort estimation: Difference between revisions

Revision as of 19:02, 7 July 2022

Revision as of 00:20, 28 October 2022

Line 226:

==Psychological issues==

{{You|section|date=October 2022}}

There are many psychological factors potentially explaining the strong tendency towards over-optimistic effort estimates that need to be dealt with to increase accuracy of effort estimates. These factors are essential even when using formal estimation models, because much of the input to these models is judgment-based. Factors that have been demonstrated to be important are: [[Wishful thinking]], [[anchoring]], [[planning fallacy]] and [[cognitive dissonance]]. A discussion on these and other factors can be found in work by Jørgensen and Grimstad.<ref>{{cite web

| author = Jørgensen, M. Grimstad, S.

Line 246 ⟶ 247:

* [[Brooks's law|Fred Brooks' law]]:

{{quotation|What one programmer can do in one month, two programmers can do in two months.|[[Fred Brooks]]|

}}

}} Adding to the fact that estimating development efforts is hard, it's worth stating that assigning more resources doesn't always help.

==Comparison of development estimation software==

Line 327 ⟶ 328:

[[Category:Software project management]]

[[Category:Software comparisons|Development estimation software]]

[[Category:Software engineering costs]]