Download as
Browse Code »

Commit 3cb1a3edd6e4e663b712db2fb63b29cf2d8992cf

Authored by Melissa Wen
2 parents 96d0cc77 1d51bf6f
Exists in master and in 3 other branches oss_2018, oss_2018_siqueira, rework_case_study

Merge branch 'oss_2018' of http://softwarepublico.gov.br/gitlab/softwarepublico/… 

…articles into oss_2018
Showing 3 changed files with 82 additions and 63 deletions   Show diff stats
icse2018/content/00-abstract.tex
  Diff comments   View file @3cb1a3e
... ... @@ -4,8 +4,8 @@ In this paper, we examined the case of a 30-month government-academia
4 4 development collaboration to map empirical practices that harmonized the
5 5 differences in open source software project management on both sides. We
6 6 evidence our adopted practices from the data collected on the repository
7   -management tool of the developed platform itself. The benefits of the empirical
8   -management model created in this project are revealed by the results of surveys
  7 +management tool of the developed platform itself. The benefits of the created empirical
  8 +management model in this project are revealed by the results of surveys
9 9 with participants on both sides of the project. These results suggest the
10 10 adoption of empirical practices based on open source ecosystems and agile
11 11 methodologies to improve the software development in context with different
... ...
icse2018/content/03-relatedwork.tex
  Diff comments   View file @3cb1a3e
... ... @@ -28,8 +28,8 @@ introduced to complex and large-scale organizations, such as the public
28 28 administration. Alleman et al. describe a production deployment for the US
29 29 government, focus on describing the methodology applied to address long term
30 30 planning and value estimation \cite{alleman2003making}. Agile methods
31   -application on the Brazilian public sector are approached by Melo et al. and De
32   -Sousa et al. \cite{melo2013agileBr,de2016using}, both are experiences limited
  31 +application on the Brazilian public sector are approached by Melo et al. \cite{melo2013agileBr} and De
  32 +Sousa et al. \cite{de2016using}, both are experiences limited
33 33 to pilot projects. Not production-ready one that will provide more accurate
34 34 data with the real world.
35 35  
... ...
icse2018/content/04-methods.tex
  Diff comments   View file @3cb1a3e
... ... @@ -2,7 +2,7 @@
2 2 \label{sec:researchdesign}
3 3  
4 4 The focus on this paper is investigating practical ways to reconcile cultural
5   -differences in software development process between academia and government,
  5 +differences in software development process between government and academia,
6 6 without modifying their internal processes. Our analysis was guided by the
7 7 following research questions:
8 8  
... ... @@ -17,86 +17,105 @@ developing an e-government platform in a government-academia collaboration?}
17 17 To answer these questions, we use as a case study the evolution project of the
18 18 SPB portal \cite{meirelles2017spb}, a government-academia collaborative
19 19 development based on open source software integration. We designed two surveys
20   -and an interview to the different roles performed by the ex-project
  20 +and an interview to the different roles performed by the project
21 21 participants and collect public data from the project development environment
22 22 available on the developed platform itself. Our research approach is detailed
23 23 in the following subsections.
24 24  
25 25 \subsection{The case study}
26 26  
27   -The project to evolve the Brazilian Public Software Portal
28   -was a partnership between government and academia held
29   -between 2014 and 2016\cite{meirelles2017spb}. To solve maintenance problems and fill
30   -design-reality gaps in the portal, the Ministry of Planning (MPOG) joined the
31   -University of Brasília (UnB) and the University of São Paulo (USP) to develop a
32   -platform based on the integration and evolution of five existing open source
33   -software.this environment was a novelty in the context of the Brazilian government, due to the technologies employed and its diverse features, including social networking (Noosfero), mailing lists (MailMan), version control system (GitLab), and source code quality monitoring (Mezuro), all integrated using a system-of-systems software (Colab).
  27 +The project to evolve the Brazilian Public Software Portal was a partnership
  28 +between government and academia held between 2014 and 2016
  29 +\cite{meirelles2017spb}. To solve maintenance problems and fill design-reality
  30 +gaps in the portal, the Ministry of Planning (MPOG) joined the University of
  31 +Brasília (UnB) and the University of São Paulo (USP) to develop a platform
  32 +based on the integration and evolution of five existing open source
  33 +software. This environment was a novelty in the context of the Brazilian
  34 +government, due to the technologies employed and its diverse features,
  35 +including social networking (Noosfero), mailing lists (MailMan), version
  36 +control system (GitLab), and source code quality monitoring (Mezuro), all
  37 +integrated using a system-of-systems software (Colab) \cite{meirelles2017spb}.
34 38  
35 39 The academic team carried out development activities in the Advanced Laboratory
36 40 of Production, Research and Innovation in Software Engineering (LAPPIS) at UnB.
37 41 The project management and development process in this laboratory is usually
38   -executed adopting empirical practices from open source communities and agile methodologies. For this project,
39   -a total of 42 undergraduate students and two coordinator-professors participated in the development team. Six IT professionals were also hired as senior developers due their experiences in open source projects and two designers specialized in User eXperience.
  42 +executed adopting empirical practices from open source communities and agile
  43 +methodologies. For this project, a total of 42 undergraduate students and two
  44 +professors participated in the development team. Six IT professionals were also
  45 +hired as senior developers due their experiences in open source projects and
  46 +two designers specialized in User eXperience.
40 47  
41 48 The government team was composed of one director, one coordinator, and two IT
42 49 analysts from a department of MPOG. Although they were responsible for the
43   -execution of this collaboration, their department generally does not
44   -execute development of ministry's software, its responsibility is
  50 +execution of this collaboration, their department generally does not execute
  51 +development of ministry's software projects, since its responsibility is
45 52 contracting and homologating software development services, following
46 53 traditional management approaches, such as the RUP, CMMI, and PMBOK.
47 54  
48 55 % Conteúdo OK melhorar construção
49   -These two aforementioned teams periodically met in person for the purpose of
50   -managing the project progress, discussing strategic/political and technical goals. Initially, these meetings took place at the ministry's headquarters and, usually, only directors and professors participated. The management of the development team was
51   -concentrated in the academic side and was organized in
52   -biweekly sprints and 4-month releases. However, with the progress of the project, this workflow proved to be inefficient. Conflicts between the internal management processes
53   -and differences in pace and goals of each institution were compromising the
54   -platform development.
  56 +The leaders of these two aforementioned teams periodically met in person for
  57 +the purpose of managing the project progress, discussing strategic and
  58 +technical goals. Initially, these meetings took place at the ministry's
  59 +headquarters and, usually, only directors and professors participated. The
  60 +management of the development team was concentrated in the academic side and
  61 +was organized in biweekly sprints and 4-month releases. With the progress of
  62 +the project, this workflow proved to be inefficient. Conflicts between the
  63 +internal management processes and differences in pace and goals of each
  64 +institution were compromising the platform development. To improve the project
  65 +management process we have adopted and evolute a set of empirical practices
  66 +based on open source ecossystems and agile methodologies, establishing an empirical
  67 +management model.
55 68  
56 69 \subsection{Survey and data collection}
57 70  
58   -We divided the UnB development team into two groups of target participants according to
59   -their roles during the project: \textit{UnB Interns} and \textit{Senior Developers}. For each
60   -group, we designed an online survey with topics related to project organization,
61   -development process, communication and relationship between members, acquired
62   -knowledge and experience with free software. We also interviewed two \textit{MPOG
63   -analysts} who directly interacted with the development team and project
64   -development process. The interview questions could be classified into four
65   -parts: Professional profile; Organization, communication and development
66   -methodologies in the context of government and project; Satisfaction with the
67   -developed platform; Lessons learned.
68   -
69   -We sent the link of the online survey through emails to 42 UnB interns (undergraduate students), who participated in any time of the project
70   -as developer receiving scholarship. We received a total of 37 responses. Their
  71 +We divided the UnB development team into two groups of target participants
  72 +according to their roles during the project: \textit{UnB Interns} and
  73 +\textit{Senior Developers}. For each group, we designed an online survey with
  74 +topics related to project organization, development process, communication and
  75 +relationship between members, acquired knowledge and experience with open
  76 +source projects. We interviewed also two \textit{MPOG analysts} who directly
  77 +interacted with the development team and project development process. The
  78 +interview questions could be classified into four parts: Professional profile;
  79 +Organization, communication and development methodologies in the context of
  80 +government and project; Satisfaction with the developed platform; Lessons
  81 +learned.
  82 +
  83 +We sent the link of the online survey through emails to 42 UnB interns
  84 +(undergraduate students), who participated in any time of the project as
  85 +developer receiving scholarship. We received a total of 37 responses. Their
71 86 average age is 25 years old and 91.9\% of them are male. Currently, 35.1\%
72 87 continue at university as undergraduate or graduate students, 18.9\% work as
73   -developer in a small company and 18.9\% in medium or large companies, 10.8\% are
74   -entrepreneurs, 8.1\% are unemployed and the others work as teachers or civil
75   -servants. 43.2\% said the SPB project was their first experience with free
76   -software.
77   -
78   -We also sent the link of the online survey through emails to eight senior developers (IT market professionals). All of them
79   -answered the questionnaire. Their average age is 32 years old and 87.5\% are
80   -male. They have an average of 11 years of experience in the IT market, and
81   -currently 62.5\% of respondents are company employees, 37.5\% are freelance
82   -developers, 25\% are master's degree students and 25\% entrepreneurs. They have
83   -worked on average in 5 companies and participated in 4 to 80 projects. They
84   -participated in this collaborative project between 7 to 24 months. 85.7\% of
85   -them had some experience with free software before the SPB project.
86   -
87   -Two MPOG IT analysts were interviewed separately.
88   -Each interview took an average of 2 hours with 28 open questions. They are more
89   -than 30 years old and have been government employees for more than 7 years.
90   -Only one of them continues working in the same ministry. For both, this
91   -collaborative project was their first experience of government-academia
92   -development collaboration.
  88 +developer in a small company and 18.9\% in medium or large companies, 10.8\%
  89 +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
  91 +open source software.
  92 +
  93 +We also sent the link of the online survey through emails to eight senior
  94 +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
  96 +11 years of experience in the IT market, and currently 62.5\% of respondents
  97 +are company employees, 37.5\% are freelance developers, 25\% are master's
  98 +degree students and 25\% entrepreneurs. They have worked on average in 5
  99 +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
  101 +experience with free software before the SPB project.
  102 +
  103 +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
  105 +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
  107 +was their first experience of government-academia development collaboration.
93 108  
94 109 Finally, we quantitatively analyze data about the development of the project,
95   -publicly available on the SPB platform. We collected from the repository manager tool of the platform all open issues and commits related to the main repository of the platform, that is, the development repositories of the integrated software were not considered.
96   -For issues, we collected:
97   -project name, author of the issue, opening date, issue title, and number of
98   -comments. We also collected informations about: total open issues, total
99   -commits, different authors of issues, total of different authors of issues,
100   -total of comments, authors of comments, total of authors other than comments.
101   -During the period from April 2015 to June 2016, 879 issues was opened by 59 distinct authors with a total of 4658 comments and 64 distinct commentators. The development team made 3256 commits in the repository provided by SPB platform, the first one in July 2014 and the last one in August 2016.
  110 +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
  112 +repository of the platform, that is, the development repositories of the
  113 +integrated software were not considered. For issues, we collected project
  114 +name, author of the issue, opening date, issue title, and number of comments.
  115 +We also collected informations about total open issues, total commits,
  116 +different authors of issues, total of different authors of issues, total of
  117 +comments, authors of comments, total of authors other than comments. During
  118 +the period from April 2015 to June 2016, 879 issues was opened by 59 distinct
  119 +authors with a total of 4,658 comments and 64 distinct commentators. The
  120 +development team made 3,256 commits in the repository provided by SPB platform.
102 121  
... ...