Commit 6bedaec7b3827196adc2d95be95f6b389a139d5f
1 parent
a2245409
Exists in
master
and in
3 other branches
[i3eSW] Add pipeline figure
Showing
2 changed files
with
2 additions
and
2 deletions
Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
... | ... | @@ -99,7 +99,7 @@ the worst political crisis after the re-democratization in Brazil. |
99 | 99 | |
100 | 100 | ## Our Continuous Delivery Pipeline |
101 | 101 | |
102 | - | |
102 | + | |
103 | 103 | |
104 | 104 | The figure represents our CD pipeline: it starts with new code arriving |
105 | 105 | which is tested and improved during as necessary as it goes through each one |
... | ... | @@ -256,7 +256,7 @@ In the first three releases, government requirements analysts were validating |
256 | 256 | all features to be released only at the end of a delivery cycle which often |
257 | 257 | took almost four months. However their superintendents requested monthly |
258 | 258 | reports about the project progress and this brought pressure on them which in |
259 | -turn put it on us. Making continuous deliveries, we really delivered | |
259 | +turn put it on us. When we started to make continuous deliveries, we really delivered | |
260 | 260 | intermediate and candidate releases. Thus, the analysts could have validate a |
261 | 261 | small set of features, making possible more accurate feedbacks and better |
262 | 262 | reports for regular meetings with their superintendents. As a result, we | ... | ... |
52.5 KB