Talk:Software development effort estimation
![]() | Computing Unassessed | |||||||||
|
![]() | The contents of the Comparison of development estimation software page were merged into Software development effort estimation on 16 April 2017. For the contribution history and old versions of the redirected page, please see its history; for the discussion at that location, see its talk page. |
Formerly untitled top-post
The references are skewed heavily toward M. Jørgensen. He(?) is clearly active in the field, but seriously, 8 references, and 0 references for Boehm!?
Honestly I had never heard of him before reading this page, though I am a student of this field. — Preceding unsigned comment added by Substantiation (talk • contribs) 03:37, 19 June 2011 (UTC)
I agree, biased by Jørgensen, I had also not heard of him. He has peer reviewed papers, fair enough, but the discussion is biased towards his approach. We should instead start with the overview (and controversy), Is estimation possible (indicate the nay-sayers), then perhaps focus on the historical development of ideas up to current thinking? — Preceding unsigned comment added by Snydersware (talk • contribs) 19:29, 22 April 2012 (UTC)
The following link, current number 25, is broken: Jørgensen, M. Grimstad, S.. "How to Avoid Impact from Irrelevant and Misleading Information When Estimating Software Development Effort". — Preceding unsigned comment added by 96.18.41.87 (talk) 14:00, 6 January 2012 (UTC)
Reference for claim
The articles says "The mean effort overrun seems to be about 30% and not decreasing over time". Can you provide a reference for this claim? I am unable to substantiate it using references provided. — Preceding unsigned comment added by Nbobbin (talk • contribs) 15:55, 16 November 2012 (UTC)
Proposed merger
Proposing merging Comparison of development estimation software into this article. Lists of notable examples of a subject are to include items with Wikipedia article already (the "notable" part). The Comparison page thus has to be reduced to only three. Especially given that, it doesn't seem like there's enough reason to justify a separate, stand-alone list. --— Rhododendrites talk | 16:01, 29 April 2014 (UTC)
Done
- merged by Klbrain. Thanks. — Rhododendrites talk \\ 10:22, 17 March 2017 (UTC)
This might deserve it's own page, but not as written
The main reason, in my view, for software development to have its own estimation page is that there was a sharp turn between traditional projects (such as construction of a large building, which can be extremely complex) and the building of complex software systems.
I'm pretty sure Drucker wrote about this long ago using the term "knowledge work" for the second category.
The thing about knowledge work is that you are rarely ever doing exactly the same thing twice. If the task hasn't changed, the technology for implemented the solution has probably changed under your feet.
Plus there is tremendously more scope for rework in software (and other creative arts, especially writing).
So it really does amount to a different body of lore, by the time you're anywhere close to doing it well.
But at present, there's not a syllable in the lead to bring this nature to the attention of the reader.
And if it isn't brought to the attention of the reader in the lead (some might think this is too OR or leading), I personally have trouble justifying this to continue existing as its own page. — MaxEnt 08:54, 13 July 2018 (UTC)