Compare View

switch
from
...
to
 
Commits (2)
Showing 2 changed files   Show diff stats
oss2018/content/03-methods.tex
  Diff comments   View file @e1ee4b2
1 1 \section{Research Design}
2 2 \label{sec:researchdesign}
3 3  
4   -% TODO: Tenho a impressão de que esse parágrafo cairia bem no último parágrafo
  4 +% TODO (by Siqueira): Tenho a impressão de que esse parágrafo cairia bem no último parágrafo
5 5 % da introdução. Pelo menos a ideia dele uma vez que resume bem o trabalho
6 6 In this paper, we studied practical alternatives to harmonize different
7 7 software development processes. We are interested in the relationship between
8 8 government and academia from the project management perspective, without the
9 9 enforcement of changing the internal processes. We present two research
10   -question that guided our work:
  10 +questions that guided our work:
11 11  
12 12 \textbf{RQ1.}\textit{How to introduce open source and agile best practices into
13 13 government-academia collaboration project?}
... ... @@ -18,43 +18,37 @@ government-academia collaborative project?}
18 18 To answer these questions, we use as a case study research method. We selected
19 19 as a case the evolution of the Brazilian Public Software portal (SPB)
20 20 \cite{meirelles2017spb}, a government-academia collaborative project based on
21   -open source software. To validate our answers, we picked three different points
22   -of views: developers, government agent, and data collected from the project
  21 +FLOSS projects. To validate our answers, we picked three different points of
  22 +views: developers, government agent, and data collected from the project
23 23 repository.
24 24  
25 25 \subsection{The case study}
26 26  
27   -%TODO:
28   -%Apresentar melhor a SPB plataforma aqui para preparar a discussão dos resultados (usar modelo IEEE Software)
29   -
30   -%TODO por parágrafo
31   -%five existing open source software (substitutir software por systems) --> As minhas modificações removeram isso, contudo vale a pena verificar
32   -%systems-of-sytems software (Colab) (substitutir software por framework) --> Não alterei uma vez que me parece inconsistente com os trabalhos antigos.
33   -
34   -The project to evolve the SPB was a partnership between government and academia
35   -held between 2014 and 2016 \cite{meirelles2017spb}. The old version of SPB
36   -suffers from maintenance problems and design-reality gaps. In this sense,
  27 +The project to evolve the SPB portal was a partnership between government and
  28 +academia held between 2014 and 2016 \cite{meirelles2017spb}. The old version of
  29 +SPB suffers from maintenance problems and design-reality gaps. In this sense,
37 30 Ministry of Planning (MPOG) decided to join the University of Brasília (UnB)
38 31 and the University of São Paulo (USP) to develop a new platform based existing
39   -open source software. However, it was required to integrate multiple software
40   -in the same system in the way that end user has a unified experience between
41   -the tools.
  32 +FLOSS projects. However, it was required to integrate multiple software in the
  33 +same system in the way that end-user has a unified experience between the
  34 +tools.
42 35  
43   -The new SPB portal was a novelty in the context of the Brazilian government,
44   -due to the technologies employed and its diverse features. The project includes
45   -social networking (Noosfero), mailing lists (MailMan), version control system
46   -(GitLab), and source code quality monitoring (Mezuro). All of this software is
47   -integrated using a system-of-systems software (Colab) [1].
  36 +In short, the SPB portal evolved into a Collaborative Development Environment
  37 +(CDE) \cite{booch2003}. It was a novelty in the context of the Brazilian
  38 +government, due to the technologies employed and its diverse features. The
  39 +project includes social networking, mailing lists, version control system, and
  40 +source code quality monitoring. All of this software is integrated using a
  41 +system-of-systems framework \cite{meirelles2017spb}.
48 42  
49   -%Colocar no discurso direto: The project hired 6 IT profectionals, and 2 designers. -> Eu acho importante falar que eles tinham backgroun em FLOSS
50 43 The academic team carried out development activities in the Advanced Laboratory
51   -of Production, Research and Innovation in Software Engineering (LAPPIS) at UnB.
52   -The laboratory born from members of Brazillian FLOSS community and from
53   -professors that worked with agile values, naturally, LAPPIS embrace the best
54   -practices of both ecosystems. For this project, the laboratory had a total of
55   -42 undergraduate interns, and two professors engaged in the development team.
56   -Finally, the project had 6 senior professionals with vast experience with
57   -FLOSS, and two designers specialized in User eXperience (UX).
  44 +of Production, Research, and Innovation in Software Engineering (LAPPIS) at
  45 +UnB. The laboratory born from a professor that is part of Brazillian FLOSS
  46 +community and another one that spreads out agile values. Thus, naturally,
  47 +LAPPIS embrace the best practices of both ecosystems. For this project, the
  48 +laboratory had a total of 42 undergraduate interns, and two professors engaged
  49 +in the development team. Finally, the project hired six senior developers with
  50 +significant experience with FLOSS communities, and two designers specialized in
  51 +User Experience (UX).
58 52  
59 53 The government team was composed of one director, one coordinator, and two IT
60 54 analysts from MPOG. They were responsible for contracts and managed the
... ... @@ -72,78 +66,61 @@ inefficient. Conflicts between the internal management processes and
72 66 differences in pace and goals of each institution were compromising the
73 67 platform development.
74 68  
75   -% TODO: Eu alterei de acordo com os comentário. Contudo, da minha experiência no projeto eu não sei se isso é verdade. Eu acho que não foi bonito como descrito aqui.
76   -We decided to adopt and assess a set of empirical practices based on FLOSS
77   -ecosystems and agile values. We tried this strategy as an attempt to improve
78   -the project management process by reducing the conflict between the government
79   -and academia. We built an experimental management model to harmonize the
80   -different cultures. During the project, the members were encouraged to try
81   -FLOSS practices in intuitive a non-systematic way. In this paper, we try to
82   -analyze and codify these practices.
  69 +Professors with senior developers' collaboration adopted, incrementally, a set
  70 +of best practices based on FLOSS ecosystems and agile values to improve the
  71 +project management process and reduce the conflict between the government and
  72 +academia. Throughout the project, the LAPPIS team built an experimental
  73 +management model to harmonize the different cultures. The development leaders
  74 +made decisions in a non-systematic way to promote the usage of these best
  75 +practices. In this paper, we analyze and codify these decisions and its
  76 +benefits.
83 77  
84 78 \subsection{Survey, Interview and Data Collection}
85 79  
86   -%UnB undergraduate interns
87   -%Online questionnaire (Não usar survey, usar sempre questionnaire)
88   -%We also interviewed
89   -%The questions are classified into categories
90   -%tirar "in the context of government and project;"
91   -
92 80 We divided the development team into two groups of participants according to
93   -their roles during the project: UnB undergraduate interns and Senior
  81 +their roles during the project: UnB undergraduate interns and senior
94 82 developers. For each set of members, we designed an online questionnaire with
95   -topics related to project organization, development process, communication and
96   -relationship between members, acquired knowledge, and experience with open
97   -source projects. We also interviewed two MPOG analysts who directly interacted
98   -with the development team and project development process. The interview
99   -questions had four parts: (1) Professional profile; (2) Organization,
100   -communication and development methodologies in the context of government; (3)
101   -Satisfaction with the developed platform; (3) Lessons learned.
102   -
103   -
104   -%falar as porcentagens sobre a profissão de todos inclusive teacher and public servants
105   -%link to online questionnaire throught e-mail
106   -We sent the online questionnaire link via email to 42 interns, all of them
107   -worked at any period of the project as a developer and received a scholarship.
108   -We received a total of 37 responses. Their average age in September 2017 is 25
109   -years old, and 92\% of them are male. Currently, 35\% continue at the university
110   -as undergraduate or graduate students, 19\% work as a developer in a small
111   -company and 19\% in medium or large enterprises, 11\% are entrepreneurs, 8% are
112   -unemployed, and the others work as teachers or civil servants. About of the
113   -interns 43\% said the SPB project was their first experience with open source
114   -software.
115   -
116   -%We also invited the 8 seniors developers to filling the oline questionnaire and all of them did.
117   -%They average age are
118   -
119   -We also sent the online questionnaire through emails to 8 senior developers (IT
120   -professionals), and all of them participated. Their average age is 32 years
121   -old, and 87\% are male. On average they have 11 years of experience in the IT
122   -market. Currently, 62\% of the interviewed have a formal job, 37\% are freelance
123   -developers, 25\% are master's degree students, and 25\% are entrepreneurs. On
124   -average they worked in 5 different companies and participated in 4 to 80
125   -projects. They joined in this collaborative project between 7 to 24 months, and
126   -86\% of them had some experience with FLOSS before the SPB project.
  83 +topics related to (1) project organization, (2) development process, (3)
  84 +communication and relationship between members, (4) acquired knowledge and (5)
  85 +experience with FLOSS projects. We also interviewed two MPOG analysts who
  86 +directly interacted with the development team and project development process.
  87 +The interview questions had four parts: (1) Professional profile;(2)
  88 +Organization, communication and development methodologies (3) Satisfaction with
  89 +the developed platform; (4) Lessons learned.
  90 +
  91 +We sent the link to the online questionnaire to 42 interns, all of them worked
  92 +at any period of the project as a developer and received a scholarship. We
  93 +received a total of 37 responses. At the time of the project, their average age
  94 +was 22 years old, and 92\% of them are male. Currently, 35\% continue at the
  95 +university as undergraduate or graduate students, 19\% work as a developer in a
  96 +small company and 19\% in medium or large enterprises, 11\% are entrepreneurs,
  97 +8\% are unemployed, 5\% are teachers, and 3\% are public servants. About of the
  98 +interns, 43\% said the SPB project was their first experience with FLOSS
  99 +projects.
  100 +
  101 +We also invited the eight IT professionals to fill the online questionnaire,
  102 +and all of them did. Their average age was 30 years old in 2015, and 87\% are
  103 +male. On average they have 11 years of experience in the IT market. Currently,
  104 +62\% of the interviewed have a formal job, 37\% are freelance developers, 25\%
  105 +are master's degree students, and 25\% are entrepreneurs. On average they
  106 +worked in 5 different companies and participated in 4 to 80 projects. They
  107 +joined in this collaborative project between 7 to 24 months, and 86\% of them
  108 +had some experience with FLOSS before the SPB project.
127 109  
128 110 We interviewed two MPOG analysts separately. Each interview took an average of
129 111 2 hours with 28 open questions. They are over 30 years old, and they have more
130   -than 7 years of experience working in the government. Only one of them
  112 +than seven years of experience working in the government. Only one of them
131 113 continues working in the same ministry. Both of the analysts said this
132 114 collaborative project was their first experience of government-academia
133 115 development collaboration.
134 116  
135   -%We collected from the repository manager all open issues and commits.
136   -%We collected from the main project repository all the issues and commits.
137   -%The number of comment authors
138   -%In the main project repository
139   -Finally, we quantitatively analyze data about the development of the project,
140   -publicly available on the SPB platform. We collected data from the repository
141   -manager all open issues and commits. We not considered the development
142   -repositories of the integrated software (e.g., Noosfero and Gitlab). Regarding
143   -the issues, we collected the total of them, project name, authors, opening
144   -date, title, and the number of comments. We also get information about the
145   -total commits, different authors per issues, the number of comments, authors of
146   -comments, the number of authors other than comments. During the period from
147   -April 2015 to June 2016, 879 issues were opened by 59 distinct authors with a
148   -total of 4,658 comments and 64 different commentators. The development team
149   -made 3,256 commits in the repository provided by SPB platform.
  117 +Finally, we analyzed, quantitatively, data about the project development,
  118 +publicly available on the SPB platform. We collected data from the central
  119 +project repository all the issues and commits. Regarding the issues, we
  120 +obtained the total of them, project name, authors, opening date, title, and the
  121 +number of comments. We also get information about the total commits, different
  122 +authors per issues, the number of comments, authors of comments, the number of
  123 +comment authors. During the period from April 2015 to June 2016, 59 distinct
  124 +authors opened 879 issues from a total of 4,658 comments and 64 different
  125 +commentators. The development team made 3,256 commits in the central project
  126 +repository.
... ...
oss2018/spb-oss-2018.bib
  Diff comments   View file @e1ee4b2
... ... @@ -230,3 +230,16 @@
230 230 year={1999},
231 231 publisher={Springer}
232 232 }
  233 +
  234 +@incollection{booch2003,
  235 +title = "Collaborative Development Environments",
  236 +series = "Advances in Computers",
  237 +publisher = "Elsevier",
  238 +volume = "59",
  239 +pages = "1 - 27",
  240 +year = "2003",
  241 +issn = "0065-2458",
  242 +doi = "https://doi.org/10.1016/S0065-2458(03)59001-5",
  243 +url = "http://www.sciencedirect.com/science/article/pii/S0065245803590015",
  244 +author = "Grady Booch and Alan W. Brown"
  245 +}
... ...