Wiki source code of Small Releases
Last modified by chrisby on 2023/10/05 14:47
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
3.1 | 1 | The team works in short iterations, each of which ends with a new product release. |
| 2 | |||
| 3 | * Release means that the software is ready for deployment, not actually deployed. Deployment of the latest release should always be technically possible; the ultimate decision to actually deploy a release is a business decision. | ||
| 4 | * The motivation for small releases is that | ||
| 5 | * stakeholders have the right to request a deployment with the latest implemented stories at any time, see [[Bill of Rights|doc:Software Engineering.Agile.Bill of Rights.WebHome]]. | ||
| 6 | * many small stable releases make debugging easier. | ||
| 7 | * feedback can be given early. |