| <?xml version="1.0" encoding="UTF-8"?> |
| <!DOCTYPE html PUBLIC "-//W3C/DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd"> |
| <!-- VERSION rmc:7.1.0 --> |
| <html xmlns="http://www.w3.org/1999/xhtml"> |
| <head> |
| <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> |
| <!-- START NON-TRANSLATABLE --> |
| <title>\xp\guidances\concepts\small_releases.xmi</title> |
| </head> |
| <!-- WARNING: do not modify the generated comments in this file below this line. They are used as markers for the import process. --> |
| <body> |
| Element Name: small_releases.xmi<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: presentationName<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:presentationName,5.762953011420275E-306 CRC: 2279552650 -->Small Releases<!-- END:presentationName,5.762953011420275E-306 --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: mainDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:mainDescription,-vcCn_ksJo5Jw27aNZb1Cvw CRC: 609473957 --><a id="XE_xp__small_releases" name="XE_xp__small_releases"></a><a id="XE_small_releases__practice_of" |
| name="XE_small_releases__practice_of"></a><a id="XE_engineering_practices__small_releases" |
| name="XE_engineering_practices__small_releases"></a> |
| <h3> |
| Description |
| </h3> |
| <p> |
| There are many developers who have spent years developing software and yet never had any of it released into use. |
| Fortunately, this situation is becoming rarer, but it still happens. There are many reasons why some software never |
| gets put into production, but often a key factor is the size of releases. Releasing software is much like integrating |
| source code changes in a project: the longer you delay it, the tougher it becomes. Releasing software into production |
| frequently is a good way of getting feedback. Users will often think of issues that they would not have without actual |
| experience using the software. Getting that feedback early enhances the overall quality of the product. |
| </p> |
| <p> |
| In XP, we recommend release cycles of three to four months at most. |
| </p> |
| <h3> |
| Benefits |
| </h3> |
| <ul> |
| <li> |
| <b>Small releases increase feedback</b>. Discrepancies between the system that is needed and the system being |
| developed are found early. |
| </li> |
| <li> |
| Putting pieces of a system into production frequently raises the quality consciousness of the project. The |
| <b>system must consistently be good enough to ship</b>. |
| </li> |
| </ul><!-- END:mainDescription,-vcCn_ksJo5Jw27aNZb1Cvw --> |
| </body> |
| </html> |
