Talk:Feature complete
 | This redirect does not require a rating on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||
| ||||||||||||||
 | This article was nominated for merging with Talk:Software_release_life_cycle on 17 December 2021. The result of the discussion (permanent link) was to merge. |
Proposing merge with "Software Release Life Cycle"
edit- The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
- The result was merge into Software release life cycle. -- Whiteguru (talk) 05:34, 17 December 2021 (UTC)
I propose this be merged into the same section as alpha and beta in Software release life cycle. -128.61.83.190 (talk) 16:37, 26 July 2010 (UTC)
I propose someone discuss this notion of feature complete and the potential for damage and the disagreement with the idea that a feature can be done when bugs are treated separately.
The reference for this term was a Microsoft book, but another Microsoft Press book called "Writing Solid Code", said that the practice of pushing off bugs to the end, permitting features to be counted as complete before they were debugged was a disaster.
In Agile, a definition of done would not be permitted for code that did not meet its design criteria, satisfy its use cases. In TDD, functionality would be demonstrated with tests. — Preceding unsigned comment added by 12.229.56.156 (talk) 20:44, 10 December 2019 (UTC)