[ieeeSW] Results of Paulo and Melissa's brainstorm

Paulo Meireles
1 parent c1aeba3c
Showing 1 changed file with 23 additions and 31 deletions Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
@@ -97,8 +97,6 @@ the widespread belief among government staff that any project in partnership
 with a University is doomed to fail, and (2) dealing with bureaucracies
 involved in the deployment process.
-<!-- Melissa: Acho que no segundo, seria bom falar: lidar com a aritmia que as burocracias do governo causavam ao nosso processo de deploy? -->
-
 Firstly, our team was not from a typical company, consisting mainly of
 undergraduate students supported senior developers and designers, all
 coordinated by two professors. Accordingly, time and resources allocation,
@@ -130,13 +128,6 @@ department responsible for the deployment routines. With each CD cycle, we
 gradually built a new relationship among all parties and, by the end of the
 project, we became active participants in the deploy operations.
-<!--
-In
-the first year, we had a group composed of 24 undergraduate students, one
-designer, and two senior developers. In 2015, our team grew to 36 students, two
-designers, eight senior developers. In the end, due to budget constraints, our
-team shrinked to 20 students, one designer, and two developers.
--->
 ## Our Continuous Delivery Pipeline
 SPB portal is a CDE with additional social features. We built system-of-systems
@@ -182,7 +173,7 @@ repository. We decided to create separate packages for each system.  Packaging
 brings portability, simplifies deployment, and enables configuration and
 permission control.
-After creating a new tag for a system, the developers informed our DevOps [4]
+After creating a new tag for a system, the developers informed our DevOps
 team, and the packaging process began. A set of scripts fully automated the
 three packaging steps aforementioned. When all of them ran successfully, the
 new packages would be ready and available for our deployment scripts.
@@ -217,23 +208,17 @@ new features and bug fixes were finally available to end users.
 ## Benefits
-Research points out many CD advantages in the industry [2, 5], such as
-accelerated time to market, building the right product, productivity and
-efficiency improvements, stable releases, and better customer satisfaction. The
-charts presented in Figure 2 show these benefits of implementing the CD in our
-project and associates them with the creation of a DevOps team.
+CD brings many advantages such as accelerated time to market, building the
+right product, productivity and efficiency improvements, stable releases, and
+better customer satisfaction [2]. The charts presented in Figure 2 show these
+benefits of CD in our project and associates them with the creation of a DevOps
+team. In the time of 30 months, we deployed a total of 84 versions. Over 64% of
+these activities happened in the second half of 2015, with the DevOps team
+creation. Besides these results, working with the government, we noticed the
+following additional benefits.
 ![The evolution of SPB releases and the team members distribution in the period.](figures/CDReleaseAndTeamEvolution.png)
-In the time of 30 months, we deployed a total of 84 versions. Over 64% of these
-activities happened in the second half of 2015, with the DevOps team creation.
-Even with the reduction of the team as a whole, in the last months of the
-project, this pace of deployment was maintained until we finished all our
-activities.
-
-Besides these results, working with the government, we noticed the following
-additional benefits.
-
 ### Strengthening Trust in the Relationship with the Government
 CD helped strengthen trust in the relationship between developers and the
@@ -300,10 +285,6 @@ of our team members did not have CD know-how, and we had few working hours
 available to build the pipeline. The construction and maintenance of the CD
 process were made possible by the key decisions to:
-<!---
-pensar em generalizar/filosofar
--->
-
 1. _Select the most experienced senior developers and some advanced students of
 the project to work on a specific DevOps team._These senior developers used
 their experience in OSS projects to craft an initial proposal for the
@@ -317,7 +298,7 @@ process on-the-fly.
 ### Overcoming Mistrust
-<!-- Precisa 'dessuavizar' o porque das mudanças de requisitos - a motivação para ela não era tão natural como as que ocorrem em métodos ágeis -->
+<!-- Tente reduzir, indo direto ao ponto para os Takeaways -->
 Adopting an unfamiliar approach requires trust. In the Ministry, traditionally,
 a software was the product delivered at the end of a development contract; they
 expected and were prepared to validate and deploy a single deliverable. This
@@ -356,10 +337,21 @@ both VE, and PE.
 1. P. Meirelles, M. Wen, A. Terceiro, R. Siqueira, L. Kanashiro, and H. Neri, "Brazilian Public Software Portal: an integrated platform for collaborative development", Proceedings of the 13th International Symposium on Open Collaboration. ACM, Article 16, 2017, 10 pages.
 1. L. Chen, "Continuous Delivery: Huge Benefits, but Challenges Too", IEEE Software, vol. 32, no. 2, 2015, pp. 50-54.
 1. J. Humble and D. Farley, "Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation", Addison-Wesley Professional, 2010.
-1. J. Davis and K. Daniels, "Effective Devops: Building a Culture of Collaboration, Affinity, and Tooling at Scale", O'Reilly Media, Inc., 2016.
-1. T. Savor, M. Douglas, M. Gentili, L. Williams, K. Beck and M. Stumm, "Continuous Deployment at Facebook and OANDA", 2016 IEEE/ACM 38th International Conference on Software Engineering Companion (ICSE-C), Austin, TX, 2016, pp. 21-30.
 <!---
+Citadas apenas para definir coisas já disseminadas
 1. G. Booch and A. Brown, A. W. "Collaborative Development Environments", Advances in Computers, vol. 59, 2003, pp. 1-27.
 1. C. B. Nielsen, P. G. Larsen, J. Fitzgerald, J. Woodcock, and J. Peleska, "Systems of Systems Engineering: Basic Concepts, Model-Based Techniques, and Research Directions", ACM Comput. Surv. 48, 2, Article 18, 2015, 41 pages.
+1. J. Davis and K. Daniels, "Effective Devops: Building a Culture of Collaboration, Affinity, and Tooling at Scale", O'Reilly Media, Inc., 2016.
+
+Estava citada apenas na introdução dos benefícios
+1. T. Savor, M. Douglas, M. Gentili, L. Williams, K. Beck and M. Stumm, "Continuous Deployment at Facebook and OANDA", 2016 IEEE/ACM 38th International Conference on Software Engineering Companion (ICSE-C), Austin, TX, 2016, pp. 21-30.
+
+Considerar:
+
+2017 State of DevOps Report
+https://puppet.com/resources/whitepaper/state-of-devops-report
+
 -->
+
+