From 09175ee53489db04c9c5770317a56fe76d17bcce Mon Sep 17 00:00:00 2001 From: Paulo Meirelles Date: Fri, 21 Apr 2017 16:39:59 -0300 Subject: [PATCH] minor corrections --- opensym2017/content/09-lessons.tex | 21 +++++++++++---------- 1 file changed, 11 insertions(+), 10 deletions(-) diff --git a/opensym2017/content/09-lessons.tex b/opensym2017/content/09-lessons.tex index ffe12c4..1e2eec0 100644 --- a/opensym2017/content/09-lessons.tex +++ b/opensym2017/content/09-lessons.tex @@ -18,19 +18,20 @@ that this tool presented functionalities that would allow MP managers to stimulate the participation of SPB service providers with gamefication practices. As we said, in order for Colab to perform the expected behavior in SPB its architecture had to be completely redefined and this caused in -practice, i) the considerable increase in the architectural complexity of the -SPB and ii) it was the subsystem that consumed the most effort and budget +practice, (i) the considerable increase in the architectural complexity of the +SPB and (ii) it was the subsystem that consumed the most effort and budget during development. Due to the computational complexity related to the SPB deployment, associated -with MP's need for product support, we made an effort to provide complete -automation of the entire deployment procedure, a result of DevOps activities. -In this way, we encapsulate all this complexity and enable the deployment of -new SPB releases through the execution of few commands, as registered in the -project documentation. Although we have provided a high degree of automation, -training workshops for the MP technical team, and a meticulous description of -the procedures in the documentation, we observed that the MP technical staff -invariably depended on our support to perform these procedures. +with the Brazilian government needs for product support, we made an effort to +provide complete automation of the entire deployment procedure, a result of +DevOps activities. In this way, we encapsulate all this complexity and enable +the deployment of new SPB releases through the execution of few commands, as +registered in the project documentation. Although we have provided a high +degree of automation, training workshops for the MP technical team, and a +meticulous description of the procedures in the documentation, we observed that +the MP technical staff invariably depended on our support to perform these +procedures. From the point of view of management and development processes, we had to develop management strategies that would accommodate different organizational -- libgit2 0.21.2