From 1acbfcf7beb882f75ee58f1087b443264d29ae47 Mon Sep 17 00:00:00 2001 From: Melissa Wen Date: Mon, 31 Jul 2017 20:00:49 -0400 Subject: [PATCH] [i3eSW] Review of the first benefit --- ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md index a5a93a3..2372d32 100644 --- a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md +++ b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md @@ -186,25 +186,26 @@ fixes were finally available to the end users. ## Benefits -Research points out many advantages of CD usage in industry, such as: +Research points out many advantages of CD usage in industry[2], 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 initial mistrust +### Responsiveness to change -The direct benefit from the CD pipeline was the fast response to changes -required by the government. That was vital for the project's renewal over the -years. We could better manage the tension between the government and the development -team. Every meeting with the government leader was delicate and resulted -on many new requirements, most of them motivated by political needs. For +Responsiveness was one of the direct benefits of adopting the CD pipeline. The +ability to react quickly to changes requested by the government was vital for +the renewal of the project over the years. Every meeting with the government +leader was resulted in new requirements, most of them motivated by political +needs. These constant changes in requirements and priorities caused discomfort +between the government and the development team. For example, once it was demanded a completely layout change because another government leader suddenly decided to make a marketing campaign about the new SPB portal. They would use undelivered requirements as a means to justify the lack of financial support, which was already planned in the first place. We believed that if we took too -long to attend their demands, the project would end. CD helped us move fast -on deploying to production, even of smaller parts of the requirements. That -way, we always had something to show on meetings, reduzindo a ansiedade em ver a versão final. For our team, made the developers more confident the +long to attend their demands, the project would end. CD helped us keep the +production environment up-to-date, even with partial versions of a feature. That +way, we always had something to show on meetings, reducing anxiety to get the platform concluded. the developers more confident the project would last a little longer and they would not go looking for other jobs. @@ -224,14 +225,13 @@ Additionally, developers worked to improve the CD pipeline in order to speed up the process of making available, in the production environment, new features for the platform. - ### Synchronicity between government and development Despite the positive impacts that the CD pipeline brought to the project, its implementation was not easy at first. The good performance of the CD pipeline depended on the synchronicity between the teams of developers and government -analysts, so that the work of one could be initiated immediately after -the delivery of the work by the other. Initially this concern was not +analysts, , so that the latter is prepared to start a step as soon as the +former concludes the previous step, and vice versa. Initially this concern was not contemplated in the agenda of the governmental team, which generated delays in the validation of the new features of the release. This situation combined with governmental bureaucracy (up to 3 days) to release access to the production -- libgit2 0.21.2