Short Releases vs Long Releases
The practice of extreme programming includes “Small Releases” - the frequent release of “short” releases of programs at intervals of several weeks.
It is understood that you need this in order to receive "feedback" from users and make changes in time. The releases themselves, as a rule, include 1-2 “features” and the correction of some (but not all) errors.
I wonder how this practice makes sense and benefit when developing commercial software products. Do users really need frequent releases? What is their interest in acting as a permanent beta tester?
It seems to me that short releases do not allow large changes to be planned in advance. How does this practice contribute (or not contribute) to preserving the ideological and architectural integrity of the product?
It is understood that you need this in order to receive "feedback" from users and make changes in time. The releases themselves, as a rule, include 1-2 “features” and the correction of some (but not all) errors.
I wonder how this practice makes sense and benefit when developing commercial software products. Do users really need frequent releases? What is their interest in acting as a permanent beta tester?
It seems to me that short releases do not allow large changes to be planned in advance. How does this practice contribute (or not contribute) to preserving the ideological and architectural integrity of the product?
')
Source: https://habr.com/ru/post/14944/
All Articles