Download as
Browse Code »

Commit dd366c216bd10e2d21633026ff4f159d6aaed928

Authored by Melissa Wen
1 parent 6047b7b0
Exists in master and in 3 other branches oss_2018, oss_2018_siqueira, rework_case_study

[i3eSW] small text formatting fixes

Showing 1 changed file with 8 additions and 8 deletions   Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
  Diff comments   View file @dd366c2
... ... @@ -53,7 +53,7 @@ conjunto de features -> testes automatizados → criação de tag → empacotame
53 53  
54 54 Figure X represents our CD pipeline. After each release, we have defined a set of features we would develop to comply with government’s requirements and then we have followed this pipeline.
55 55  
56   -#### Automated tests
  56 +### Automated tests
57 57  
58 58 [//]: # (TODO - Rever a escrita desta ideia com mais calma)
59 59 [//]: # (TODO - Adicionar que as mudanças no Colab quebravam todos os plugins.)
... ... @@ -81,7 +81,7 @@ After creating a new tag for one component, the DevOps team was notified and pac
81 81  
82 82 After all these scripts have run successfully, the new packages would be ready to use by our subsequent deployment scripts.
83 83  
84   -#### Validation Environment
  84 +### Validation Environment
85 85  
86 86 [//]: # (TODO - Mencionar que a ferramenta era baseada em Chef - Dá um peso importante.)
87 87  
... ... @@ -102,13 +102,13 @@ We had to handle many tensions between development and political issues. Our CD
102 102  
103 103 [//]: # (TODO - Melhorar título - Ideias: Response to mistrust)
104 104  
105   -#### Response to tensions
  105 +### Response to tensions
106 106  
107 107 [//]: # (TODO - Decisão do secretario acima do diretor)
108 108  
109 109 The direct benefit from the CD pipeline was the fast response to the changes required by the government. That was vital for the project’s renewal over the years. We could manage the tension between the government and the development team better. Every meeting with the government leader was delicate and resulted on many new requirements, most of them motivated by political needs. For example, once it was demanded a completely layout change because one director suddenly decided to make a marketing campaign about the portal. They would use undelivered requirements as a means to suggest the project’s cancellation. We believed that if we took too long to attend their demands, the project would end. CD helped us to move fast on deploying to production, even of smaller parts of the requirements. That way, we always had something to show on the meetings, reducing their eagerness to end the project. For our team, it made the developers more confident the project would last a little longer and they would not go looking for another jobs.
110 110  
111   -#### Build client’s trust
  111 +### Build client’s trust
112 112  
113 113 After we established the CD, the government agents started to be more confident in our work. First, because they noticed that each new deploy made by us in the VE was stable and reliable. Second, they could see new features fast since we constantly updated the VE based on their feedback. This made our relation strong and in moments that needed quick action they would rather give us access to production.
114 114  
... ... @@ -124,13 +124,13 @@ Taking on CD responsibilities had a significant impact on the team. We did not h
124 124  
125 125 The seniors were crucial at this point. They came up with an initial solution to get us started. That already enabled us to automatize the deploy, even though the process was still rudimentary. We had to evolve our solution on-the-fly. We dedicated a few developers to this task.
126 126  
127   -#### Handling inexperienced teams
  127 +### Handling inexperienced teams
128 128  
129 129 After the developers learned how CD worked, it was difficult to pass the knowledge along to other teammates. We tried to mitigate this by encouraging a member's migration to the DevOps team. Further research on how to effectively spread knowledge across inexperienced developers in a scenario with a high turnover are needed.
130 130  
131 131 [//]: # (TODO - Refazer título abaixo - ideias: overcoming the challenges / overcoming the mistrust)
132 132  
133   -#### Building trust
  133 +### Building trust
134 134  
135 135 [//]: # (TODO - Deixar claro que government = os técnicos , análista ou agentes do governo, conforme for padronizado no texto)
136 136  
... ... @@ -138,13 +138,13 @@ In the project’s first half we struggled with deploy related problems in the g
138 138  
139 139 ---
140 140  
141   -#### Sobre a chamada
  141 +## Sobre a chamada
142 142  
143 143 Release Engineering 3.0 – Call for Papers: https://www.computer.org/software-magazine/2016/12/14/release-engineering-3-0-call-for-papers/
144 144 Orientações:
145 145 https://www.computer.org/web/peer-review/magazines
146 146  
147   -#### TODO
  147 +### TODO
148 148 * [ ] Manter distância de qualquer análise política ou opinião. Relatar os fatos que podem ser facilmente verificados
149 149 * [x] Lembrar que o SPB também tinha uma pegada social, uma vez que produzia bolsas para mais de 50 alunos. Podíamos ter acatado o fim do projeto, mas resistimos pelo alunos e pelo fato de que acreditávamos que o nosso trabalho era útil para a sociedade. Abortado por não fazer sentido
150 150 * [ ] Procurar uma referência meio fortinho em inglês que indique a instabilidade política do Brasil
... ...