Commit 7c31d240dd4d8da132ab36610157b8c2d7a7d02d

Authored by Melissa Wen
1 parent 00ede063

[oss-2018] todo about Fabio - related works and research design

oss2018/content/02-relatedwork.tex
@@ -10,6 +10,11 @@ @@ -10,6 +10,11 @@
10 %sobre FLOSS e talvez possam dizer que a gente não se 'enquadra' na conferência. 10 %sobre FLOSS e talvez possam dizer que a gente não se 'enquadra' na conferência.
11 %Não acho que precisamos tirar a parte 'agile', mas precisamos ser mais conciso 11 %Não acho que precisamos tirar a parte 'agile', mas precisamos ser mais conciso
12 %sobre isso 12 %sobre isso
  13 +
  14 +%Sugestão do Fabio: Colocar referências de trabalho que conseguiram conciliar
  15 +%ou que reportam dificuldade em conciliar ou aplicar processos de gerenciamento
  16 +%em um projeto de colaboração
  17 +
13 Discussions on how to introduce new management methods into an organization are 18 Discussions on how to introduce new management methods into an organization are
14 present in several papers. Nerur et al. identify the critical issues that involve 19 present in several papers. Nerur et al. identify the critical issues that involve
15 migrating from traditional to agile by comparing main practices of the two 20 migrating from traditional to agile by comparing main practices of the two
oss2018/content/03-methods.tex
@@ -2,28 +2,32 @@ @@ -2,28 +2,32 @@
2 \label{sec:researchdesign} 2 \label{sec:researchdesign}
3 3
4 The focus of this paper is investigating practical ways to conciliate cultural 4 The focus of this paper is investigating practical ways to conciliate cultural
5 -differences in software development process between government and academia, 5 +differences in software development processes between government and academia,
6 without modifying their internal processes. Our analysis was guided by the 6 without modifying their internal processes. Our analysis was guided by the
7 following research questions: 7 following research questions:
8 8
9 -\textbf{RQ1.}\textit{What practices based on open source development experiences would  
10 -help to combine teams with different management processes in a 9 +\textbf{RQ1.}\textit{How to introduce open source and agile best practices into
11 government-academia collaboration project?} 10 government-academia collaboration project?}
12 11
13 -  
14 -\textbf{RQ2.}\textit{How do open source development practices benefit the process of  
15 -developing an e-government platform in a government-academia collaboration?} 12 +\textbf{RQ2.}\textit{What practices would favor effective team management in
  13 +government-academia collaborative project?}
16 14
17 To answer these questions, we use as a case study the evolution project of the 15 To answer these questions, we use as a case study the evolution project of the
18 SPB portal \cite{meirelles2017spb}, a government-academia collaborative 16 SPB portal \cite{meirelles2017spb}, a government-academia collaborative
19 development based on open source software integration. We designed two surveys 17 development based on open source software integration. We designed two surveys
20 and an interview to the different roles performed by the project 18 and an interview to the different roles performed by the project
21 -participants and collect public data from the project development environment  
22 -available on the developed platform itself. Our research approach is detailed  
23 -in the following subsections. 19 +participants and we collected public data from the project development
  20 +environment. Our research approach is detailed in the following subsections.
24 21
25 \subsection{The case study} 22 \subsection{The case study}
26 23
  24 +%TODO:
  25 +%Apresentar melhor a SPB plataforma aqui para preparar a discussão dos resultados (usar modelo IEEE Software)
  26 +
  27 +%TODO por parágrafo
  28 +%five existing open source software (substitutir software por systems)
  29 +%systems-of-sytems software (Colab) (substitutir software por framework)
  30 +
27 The project to evolve the Brazilian Public Software Portal was a partnership 31 The project to evolve the Brazilian Public Software Portal was a partnership
28 between government and academia held between 2014 and 2016 32 between government and academia held between 2014 and 2016
29 \cite{meirelles2017spb}. To solve maintenance problems and fill design-reality 33 \cite{meirelles2017spb}. To solve maintenance problems and fill design-reality
@@ -36,6 +40,10 @@ including social networking (Noosfero), mailing lists (MailMan), version @@ -36,6 +40,10 @@ including social networking (Noosfero), mailing lists (MailMan), version
36 control system (GitLab), and source code quality monitoring (Mezuro), all 40 control system (GitLab), and source code quality monitoring (Mezuro), all
37 integrated using a system-of-systems software (Colab) \cite{meirelles2017spb}. 41 integrated using a system-of-systems software (Colab) \cite{meirelles2017spb}.
38 42
  43 +%Não usar empirical practices => best practices
  44 +%undergraduate students => undergraduate interns
  45 +%Colocar no discurso direto: The project hired 6 IT profectionals, and 2 designers.
  46 +
39 The academic team carried out development activities in the Advanced Laboratory 47 The academic team carried out development activities in the Advanced Laboratory
40 of Production, Research and Innovation in Software Engineering (LAPPIS) at UnB. 48 of Production, Research and Innovation in Software Engineering (LAPPIS) at UnB.
41 The project management and development process in this laboratory are usually 49 The project management and development process in this laboratory are usually
@@ -45,14 +53,20 @@ professors participated in the development team. Six IT professionals were also @@ -45,14 +53,20 @@ professors participated in the development team. Six IT professionals were also
45 hired as senior developers due to their experiences in open source projects and 53 hired as senior developers due to their experiences in open source projects and
46 two designers specialized in User eXperience. 54 two designers specialized in User eXperience.
47 55
  56 +%(Melhorar a frase) Although they were responsible... Sugestão de sequência: theses government servants did not develop software. Their responsability was contracting...
  57 +
48 The government team was composed of one director, one coordinator, and two IT 58 The government team was composed of one director, one coordinator, and two IT
49 -analysts from a department of MPOG. Although they were responsible for the 59 +analysts from MPOG. Although they were responsible for the
50 execution of this collaboration, their department generally does not execute 60 execution of this collaboration, their department generally does not execute
51 development of ministry's software projects, since its responsibility is 61 development of ministry's software projects, since its responsibility is
52 contracting and homologating software development services, following 62 contracting and homologating software development services, following
53 traditional management approaches, such as the RUP, CMMI, and PMBOK. 63 traditional management approaches, such as the RUP, CMMI, and PMBOK.
54 64
55 -% Conteúdo OK melhorar construção 65 +%Met in person to manage...
  66 +%To improve the project management process we have adopted and evolute a set of empirical practices based on open source ecosystems and agile methodologies, establishing an empirical management model.
  67 +%Melhorar frase como um todo tirando o 'we' (diferenciar autor (we) do coordenador do projeto): To improve the project management process we have adopted and evolved a set of empirical practices based on open source ecosystems and agile methodologies, establishing an empirical management model.
  68 +%Sugestão de conteúdo para finalizar a última frase
  69 +%"Ao longo do projeto, os seus responsáveis foram experimentando e testando práticas coletadas do OSS de forma intuitiva e não-sistemática. Neste paper tentamos analisar e sistematizar essas melhores práticas."
56 The leaders of these two aforementioned teams periodically met in person for 70 The leaders of these two aforementioned teams periodically met in person for
57 the purpose of managing the project progress, discussing strategic and 71 the purpose of managing the project progress, discussing strategic and
58 technical goals. Initially, these meetings took place at the ministry's 72 technical goals. Initially, these meetings took place at the ministry's
@@ -68,6 +82,12 @@ management model. @@ -68,6 +82,12 @@ management model.
68 82
69 \subsection{Survey and data collection} 83 \subsection{Survey and data collection}
70 84
  85 +%UnB undergraduate interns
  86 +%Online questionnaire (Não usar survey, usar sempre questionnaire)
  87 +%We also interviewed
  88 +%The questions are classified into categories
  89 +%tirar "in the context of government and project;"
  90 +
71 We divided the UnB development team into two groups of target participants 91 We divided the UnB development team into two groups of target participants
72 according to their roles during the project: \textit{UnB Interns} and 92 according to their roles during the project: \textit{UnB Interns} and
73 \textit{Senior Developers}. For each group, we designed an online survey with 93 \textit{Senior Developers}. For each group, we designed an online survey with
@@ -80,6 +100,12 @@ Organization, communication and development methodologies in the context of @@ -80,6 +100,12 @@ Organization, communication and development methodologies in the context of
80 government and project; Satisfaction with the developed platform; Lessons 100 government and project; Satisfaction with the developed platform; Lessons
81 learned. 101 learned.
82 102
  103 +%UnB interns (undergraduate students) => interns
  104 +%their average age [in september 2017] are...
  105 +%arredondar as casas das porcentagem, nada depois da virgula 43,2% => 43%
  106 +%falar as porcentagens sobre a profissão de todos inclusive teacher and public servants
  107 +%link to online questionnaire throught e-mail
  108 +
83 We sent the link to the online survey through emails to 42 UnB interns 109 We sent the link to the online survey through emails to 42 UnB interns
84 (undergraduate students), who participated in any time of the project as 110 (undergraduate students), who participated in any time of the project as
85 developer receiving a scholarship. We received a total of 37 responses. Their 111 developer receiving a scholarship. We received a total of 37 responses. Their
@@ -90,6 +116,9 @@ are entrepreneurs, 8.1\% are unemployed and the others work as teachers or @@ -90,6 +116,9 @@ are entrepreneurs, 8.1\% are unemployed and the others work as teachers or
90 civil servants. 43.2\% said the SPB project was their first experience with 116 civil servants. 43.2\% said the SPB project was their first experience with
91 open source software. 117 open source software.
92 118
  119 +%We also invited the 8 seniors developers to filling the oline questionnaire and all of them did.
  120 +%They average age are
  121 +
93 We also sent the link to the online survey through emails to eight senior 122 We also sent the link to the online survey through emails to eight senior
94 developers (IT professionals). All of them answered the questionnaire. 123 developers (IT professionals). All of them answered the questionnaire.
95 Their average age is 32 years old and 87.5\% are male. They have an average of 124 Their average age is 32 years old and 87.5\% are male. They have an average of
@@ -100,12 +129,18 @@ companies and participated in 4 to 80 projects. They participated in this @@ -100,12 +129,18 @@ companies and participated in 4 to 80 projects. They participated in this
100 collaborative project between 7 to 24 months. 85.7\% of them had some 129 collaborative project between 7 to 24 months. 85.7\% of them had some
101 experience with free software before the SPB project. 130 experience with free software before the SPB project.
102 131
  132 +
103 Two MPOG IT analysts were interviewed separately. Each interview took an 133 Two MPOG IT analysts were interviewed separately. Each interview took an
104 average of 2 hours with 28 open questions. They are more than 30 years old and 134 average of 2 hours with 28 open questions. They are more than 30 years old and
105 have been government employees for more than 7 years. Only one of them 135 have been government employees for more than 7 years. Only one of them
106 continues working in the same ministry. For both, this collaborative project 136 continues working in the same ministry. For both, this collaborative project
107 was their first experience of government-academia development collaboration. 137 was their first experience of government-academia development collaboration.
108 138
  139 +%We collected from the repository manager all open issues and commits.
  140 +%We collected from the main project repository all the issues and commits.
  141 +%The number of comment authors
  142 +%In the main project repository
  143 +
109 Finally, we quantitatively analyze data about the development of the project, 144 Finally, we quantitatively analyze data about the development of the project,
110 publicly available on the SPB platform. We collected from the repository 145 publicly available on the SPB platform. We collected from the repository
111 manager tool of the platform all open issues and commits related to the main 146 manager tool of the platform all open issues and commits related to the main