New benefits :)

Rodrigo Siqueira de Melo
1 parent da36ec8d
Showing 1 changed file with 38 additions and 4 deletions Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
@@ -193,9 +193,10 @@ fixes are finally available to end users.
 ## Benefits
-We had to handle many tensions between development and political issues. Our CD
-pipeline gave us strong mechanisms to tackle most of the problems. As a result
-we came with some benefits from our decision to adopt CD.
+Research points out many advantages of CD usage in industry, such as:
+accelerated time to market, building the right product, productivity and
+efficiency improvements, reliable releases and better customer satisfaction.
+Working with the government, we noticed the following additional benefits.
 ### Response to mistrust
@@ -231,8 +232,41 @@ developers lost track of what happened after code was delivered. After adopting
 CD, they felt more responsible for what was getting into production. CD
 influenced developers on taking ownership of the project. In the end of the
 project, we noticed that the entire team was working to improve the CD pipeline
-since they wanted to their new features in production.
+since they want to their new features in production.
+Interestingly, the CD pipeline also made the government requirements analysts
+feel more responsible for the project. They were an active part of the pipeline
+and that engaged them on the whole process. In the end, they were even actively
+creating issues and discussing them during the development process.
+
+
+[//]: # (TODO - depois deles entrarem de fato no pipeline, ou seja, validar em ambiente de homologação, criando issues e comentando nas issues do repositório é que de nosso processo empírico de desenvolvimento predominou até o fim do processo)
+
+
+### 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.
 ## Challenges
	@@ -193,9 +193,10 @@ fixes are finally available to end users.		@@ -193,9 +193,10 @@ fixes are finally available to end users.
193		193
194	## Benefits	194	## Benefits
195		195
196	-We had to handle many tensions between development and political issues. Our CD
197	-pipeline gave us strong mechanisms to tackle most of the problems. As a result
198	-we came with some benefits from our decision to adopt CD.	196	+Research points out many advantages of CD usage in industry, such as:
		197	+accelerated time to market, building the right product, productivity and
		198	+efficiency improvements, reliable releases and better customer satisfaction.
		199	+Working with the government, we noticed the following additional benefits.
199		200
200	### Response to mistrust	201	### Response to mistrust
201		202
	@@ -231,8 +232,41 @@ developers lost track of what happened after code was delivered. After adopting		@@ -231,8 +232,41 @@ developers lost track of what happened after code was delivered. After adopting
231	CD, they felt more responsible for what was getting into production. CD	232	CD, they felt more responsible for what was getting into production. CD
232	influenced developers on taking ownership of the project. In the end of the	233	influenced developers on taking ownership of the project. In the end of the
233	project, we noticed that the entire team was working to improve the CD pipeline	234	project, we noticed that the entire team was working to improve the CD pipeline
234	-since they wanted to their new features in production.	235	+since they want to their new features in production.
235		236
		237	+Interestingly, the CD pipeline also made the government requirements analysts
		238	+feel more responsible for the project. They were an active part of the pipeline
		239	+and that engaged them on the whole process. In the end, they were even actively
		240	+creating issues and discussing them during the development process.
		241	+
		242	+
		243	+[//]: # (TODO - depois deles entrarem de fato no pipeline, ou seja, validar em ambiente de homologação, criando issues e comentando nas issues do repositório é que de nosso processo empírico de desenvolvimento predominou até o fim do processo)
		244	+
		245	+
		246	+### CD pipeline protocol between Government and Development
		247	+
		248	+When we were starting to use our CD pipeline, the acceptance tests became a
		249	+bottleneck. The government requirements analysts were busy and that resulted in
		250	+delaying their review of the new features. Additionally, when they accepted the
		251	+new code, delays of up to 3 days could happen before we could get access to the
		252	+production environment. As the CD pipeline became clearer for them, we noticed
		253	+they started to better organize themselves to speed up their review and
		254	+production access requirement. The government bureaucracy was not a bottleneck
		255	+anymore.
		256	+
		257	+### Work in small batches tranquilized the government requirements analysts
		258	+
		259	+1 - Nas primeiras 3 releases, eles validavam a release quase inteira de uma
		260	+vez, o que gerava uma pressão neles, por terem que reportar mensalmente o
		261	+status do projetos aos seus superiores (repassavam a pressão do superior deles
		262	+para nós)
		263	+
		264	+2- Com as entregas contínuas, de fato, houve entregas de releases
		265	+intermediárias e candidatas, de forma que o conjunto de funcionalidades a serem
		266	+validade, por entrega, era pequeno, possibilitando um bom feedback via as
		267	+issues do repositório, bem como relatórios mensais nas reuniões periódicas com
		268	+seus superiores (deixaram de repassar tal pressão). Ou seja, eles também
		269	+passaram a ter a confiança dos seus superiores na condução do projeto/processo.
236		270
237	## Challenges	271	## Challenges
238		272