Information Technology Reference
In-Depth Information
Figure 16-1. Using short build→test→deploy cycles
It's harder to estimate when long, drawn-out development cycles will complete than shorter
“baby step” development increments as advocated in
Figure 16-1
.
As
Figure 16-2
shows,
what almost inevitably happens with long, drawn-out development cycles is that testing is
done at the last minute and it ultimately takes longer to deliver a large feature than intended.
At the same time, the shorter testing period sacrifices quality, and this can lead to the “throw
it over the wall to operations” scenario where applications work fine in development but
don't work in production. Configuration management tools like Chef try to address this prob-
lem.
