Commit 9047e0e911ea70d57584802a11ed9966454d3e3d
1 parent
31e674b9
Exists in
master
and in
3 other branches
Adding a draft to show some data
Showing
2 changed files
with
19 additions
and
5 deletions
Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
| @@ -98,8 +98,8 @@ with a University is doomed to fail, and (2) dealing with bureaucracies | @@ -98,8 +98,8 @@ with a University is doomed to fail, and (2) dealing with bureaucracies | ||
| 98 | involved in the deployment process. | 98 | involved in the deployment process. |
| 99 | <!-- Melissa: Acho que no segundo, seria bom falar: lidar com a aritmia que as burocracias do governo causavam ao nosso processo de deploy? --> | 99 | <!-- Melissa: Acho que no segundo, seria bom falar: lidar com a aritmia que as burocracias do governo causavam ao nosso processo de deploy? --> |
| 100 | 100 | ||
| 101 | -Firstly, our team was not from a typical company, consisting from | ||
| 102 | -undergraduate students coordinated by two professors. Accordingly, time and | 101 | +Firstly, our team was not from a typical company, consisting mainly of |
| 102 | +undergraduate students supported senior developers and designers, all coordinated by two professors. Accordingly, time and | ||
| 103 | resources allocation, accountability, and team continuity might be construed | 103 | resources allocation, accountability, and team continuity might be construed |
| 104 | as "unprofessional". On the government side, the SPB portal evolution was the | 104 | as "unprofessional". On the government side, the SPB portal evolution was the |
| 105 | first software development collaboration between universities and the Ministry | 105 | first software development collaboration between universities and the Ministry |
| @@ -146,7 +146,7 @@ That solution orchestrates these multiple components and allowed us to smoothly | @@ -146,7 +146,7 @@ That solution orchestrates these multiple components and allowed us to smoothly | ||
| 146 | provide a unified interface for final users, including single sign-on and | 146 | provide a unified interface for final users, including single sign-on and |
| 147 | global searches [1]. | 147 | global searches [1]. |
| 148 | 148 | ||
| 149 | - | 149 | + |
| 150 | 150 | ||
| 151 | The SPB portal deployment follows a typical CD pipeline [3], adapted to the | 151 | The SPB portal deployment follows a typical CD pipeline [3], adapted to the |
| 152 | technical and organizational context of our project and the use of OSS best | 152 | technical and organizational context of our project and the use of OSS best |
| @@ -225,8 +225,20 @@ fixes were finally available to end users. | @@ -225,8 +225,20 @@ fixes were finally available to end users. | ||
| 225 | 225 | ||
| 226 | Research points out many CD advantages in the industry [2, 5], such as | 226 | Research points out many CD advantages in the industry [2, 5], such as |
| 227 | accelerated time to market, building the right product, productivity and | 227 | accelerated time to market, building the right product, productivity and |
| 228 | -efficiency improvements, stable releases, and better customer satisfaction. | ||
| 229 | -Working with the government, we noticed the following additional benefits. | 228 | +efficiency improvements, stable releases, and better customer satisfaction. The |
| 229 | +charts presented in Figure 2 show these benefits of implementing the CD in our | ||
| 230 | +project and associates them with the creation of a DevOps team. | ||
| 231 | + | ||
| 232 | + | ||
| 233 | + | ||
| 234 | +In the time of 30 months, we deployed a total of 84 versions. Over 64% of these | ||
| 235 | +activities happened in the second half of 2015, when the DevOps team was | ||
| 236 | +created. Even with the reduction of the team as a whole, in the last months of | ||
| 237 | +the project, this pace of deployment was maintained until we finished all our | ||
| 238 | +activities. | ||
| 239 | + | ||
| 240 | +Besides these results, working with the government, we noticed the following | ||
| 241 | +additional benefits. | ||
| 230 | 242 | ||
| 231 | ### Strengthening Trust in the Relationship with the Government | 243 | ### Strengthening Trust in the Relationship with the Government |
| 232 | 244 | ||
| @@ -289,11 +301,13 @@ deployment process and kept the project alive. We now look at the lessons learne | @@ -289,11 +301,13 @@ deployment process and kept the project alive. We now look at the lessons learne | ||
| 289 | 301 | ||
| 290 | ### Build CD From Scratch | 302 | ### Build CD From Scratch |
| 291 | 303 | ||
| 304 | +<!--- | ||
| 292 | We started with a team composed of 24 undergraduate students, one designer, and | 305 | We started with a team composed of 24 undergraduate students, one designer, and |
| 293 | two senior developers. In 2015, our team grew to 36 students, two designers, | 306 | two senior developers. In 2015, our team grew to 36 students, two designers, |
| 294 | eight senior developers. For 2016, due to budget constraints, our team shrinked | 307 | eight senior developers. For 2016, due to budget constraints, our team shrinked |
| 295 | to 20 students, one designer, and two developers; however, in the last 3 | 308 | to 20 students, one designer, and two developers; however, in the last 3 |
| 296 | months, only 6 students closed the project. | 309 | months, only 6 students closed the project. |
| 310 | +--> | ||
| 297 | 311 | ||
| 298 | Taking on the responsibility for implementing CD impacted the whole team. Most | 312 | Taking on the responsibility for implementing CD impacted the whole team. Most |
| 299 | of our team members did not have CD know-how and we had few working hours | 313 | of our team members did not have CD know-how and we had few working hours |
1.8 MB