From d9e303aa3808b8c59fb05cb28738478df38c1360 Mon Sep 17 00:00:00 2001 From: Melissa Wen Date: Sat, 29 Jul 2017 23:24:51 -0400 Subject: [PATCH] [i3eSW] Benefits text --- ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md | 44 ++++++++++++++++++++++---------------------- 1 file changed, 22 insertions(+), 22 deletions(-) diff --git a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md index 4fa68bc..2a86d92 100644 --- a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md +++ b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md @@ -245,28 +245,28 @@ creating issues and discussing them during the development process. ### CD pipeline protocol between Government and Development -When we were starting to use our CD pipeline, the acceptance tests became a -bottleneck. The government requirements analysts were busy and that resulted in -delaying their review of the new features. Additionally, when they accepted the -new code, delays of up to 3 days could happen before we could get access to the -production environment. As the CD pipeline became clearer for them, we noticed -they started to better organize themselves to speed up their review and -production access requirement. The government bureaucracy was not a bottleneck -anymore. - -### Work in small batches tranquilized the government requirements analysts - -1 - Nas primeiras 3 releases, eles validavam a release quase inteira de uma -vez, o que gerava uma pressão neles, por terem que reportar mensalmente o -status do projetos aos seus superiores (repassavam a pressão do superior deles -para nós) - -2- Com as entregas contínuas, de fato, houve entregas de releases -intermediárias e candidatas, de forma que o conjunto de funcionalidades a serem -validade, por entrega, era pequeno, possibilitando um bom feedback via as -issues do repositório, bem como relatórios mensais nas reuniões periódicas com -seus superiores (deixaram de repassar tal pressão). Ou seja, eles também -passaram a ter a confiança dos seus superiores na condução do projeto/processo. +In the beginning of the CD pipeline use, a bottleneck arose at the acceptance +tests step due to delays in reviewing new features and starting the next step. +These delays occured because the government analysts, responsible for +reviewing, were sometimes busy or didn't have schedule this work. Furthermore, +after the acceptance of the new code, there was a bureaucracy in the government +IT infrastructure that often made us to wait until 3 days to get the production +environment access and then to start the deployment step. This problem was +softened when we clarify our pipeline for these analysts and they organized +their schedule to speed up reviews and production access requests. + +### Work in small batches developed trust in our relation with government analysts + +In the first three releases, government requirements analysts were validating +all features to be released only at the end of a delivery cycle which often +took almost four months. However their superintendents requested monthly +reports about the project progress and this brought pressure on them which in +turn put it on us. Making continuous deliveries, we really delivered +intermediate and candidate releases. Thus, the analysts could have validate a +small set of features, making possible more accurate feedbacks and better +reports for regular meetings with their superintendents. As a result, we +gained their trust and they also gained trust of their chiefs about the SPB +project management. ## Challenges -- libgit2 0.21.2