Download as
Browse Code »

Commit 85cdabf670edefec2bd51ebe5a240ffa893268cd

Authored by Paulo Meireles
1 parent 43d54ec6
Exists in master and in 2 other branches oss_2018, rework_case_study

[oss-2018] removing results subsections

Showing 1 changed file with 26 additions and 28 deletions   Show diff stats
oss2018/content/04-results.tex
  Diff comments   View file @85cdabf
... ... @@ -24,21 +24,20 @@ practices that made these decisions concrete. We use data collected from the
24 24 central repository to map best practices and, with the respondents' answers, we
25 25 analyzed how each decision benefited the project collaboration.
26 26  
27   -
28   -\subsection{Use of system under development to develop the system itself}
29   -
30   -UnB team released the first version of the new SPB portal nine months after the
31   -project beginning. Due to the platform features for software development and
32   -social network, the UnB coordinators decided to use the platform under
33   -construction to develop the system itself. Gradually, in addition to
34   -development activities, government and academia migrated the project management
35   -and the communication between teams to the portal environment. In short, the
36   -wiki feature was used for logging meetings, defining goals, planning sprints,
37   -documenting deployment procedures and user guides. The issue tracker was used
38   -for discussing requirements, monitoring features under development, requesting
39   -and recording changes, and validating the delivered functionalities. Finally,
40   -the mailing list was used by the entire team for collaborative construction of
41   -requirements, defining schedules, and scheduling meetings between institutions.
  27 +The development team decides to \textbf{use of system under development to
  28 +develop the system itself}. UnB team released the first version of the new SPB
  29 +portal nine months after the project beginning. Due to the platform features
  30 +for software development and social network, the UnB coordinators decided to
  31 +use the platform under construction to develop the system itself. Gradually, in
  32 +addition to development activities, government and academia migrated the
  33 +project management and the communication between teams to the portal
  34 +environment. In short, the wiki feature was used for logging meetings, defining
  35 +goals, planning sprints, documenting deployment procedures and user guides. The
  36 +issue tracker was used for discussing requirements, monitoring features under
  37 +development, requesting and recording changes, and validating the delivered
  38 +functionalities. Finally, the mailing list was used by the entire team for
  39 +collaborative construction of requirements, defining schedules, and scheduling
  40 +meetings between institutions.
42 41  
43 42 Our surveys report Mailing list (100\%) and Issue Tracker (62.5\%) as the main
44 43 means of interaction between senior developers and interns. Developers and MPOG
... ... @@ -81,15 +80,15 @@ well as in the portal itself. When necessary, we can access the tools and find
81 80 out how we develop a solution. We can recover these positive points.''}.
82 81  
83 82  
84   -\subsection{Bring together government staff and development team}
85   -
86   -At the beginning of the project, the interviewed MPOG analysts did not
87   -participate in any direct interaction with any UnB representative, even though
88   -they were the ones in charge of the government in ensuring the collaboration
89   -agreement and the delivery of the products. Because of this, they relied on
90   -feedback from their superiors on inter-institutional meetings. They reported
91   -that there was significant communication noise in the internal dialogues with
92   -their superiors, as well as between their superiors and the development team.
  83 +The project coordinator works to \textbf{brings together government staff and
  84 +development team}. At the beginning of the project, the interviewed MPOG
  85 +analysts did not participate in any direct interaction with any UnB
  86 +representative, even though they were the ones in charge of the government in
  87 +ensuring the collaboration agreement and the delivery of the products. Because
  88 +of this, they relied on feedback from their superiors on inter-institutional
  89 +meetings. They reported that there was significant communication noise in the
  90 +internal dialogues with their superiors, as well as between their superiors and
  91 +the development team.
93 92  
94 93 In the second phase of the project, these analysts came to represent the
95 94 government directly in the dialogues with the academia, and they started to
... ... @@ -135,10 +134,9 @@ qualified, the code had quality, and the project was well executed. So in
135 134 practice, our difficulty interpreting the technical details did not impact the
136 135 releases planning.''}.
137 136  
138   -\subsection{Divide the development team into priority fronts, and for each one,
139   -hire at least one specialist from the IT market}
140   -
141   -The development team had four work areas divided by the main demands of the
  137 +The technical leaders \textbf{divide the development team into priority fronts,
  138 +and for each one, hire at least one specialist from the IT market}. The
  139 +development team had four work areas divided by the main demands of the
142 140 project: User Experience, DevOps, Integration of Systems, and Social
143 141 Networking. For each of them, at least one professional in the IT market was
144 142 hired to raise the quality of the product. Senior developers have a vast
... ...