Software Público Brasileiro

\section{Research Design}
\label{sec:researchdesign}

Our analysis was guided by the following research questions:

\textbf{RQ1.}{What practices based on open source development experiences would
help to combine teams with different management processes in a
government-academia collaboration project?}


\textbf{RQ2.}{How do open source development practices benefit the process of
developing an e-government platform in a government-academia collaboration?}

To answer these questions, we use as a case study the evolution project of the
SPB portal \cite{meirelles2017spb}, a government and academia collaborative
development based on open source software integration. From this project, we
collect public data from the project development environment available on the
developed platform itself, and conduct two surveys and an interview aimed at the
different roles performed by the ex-project participants, as detailed in the
following subsections

\subsection{The case estudy}

The project to evolve the Brazilian Public Software Portal
\cite{meirelles2017spb} was a partnership between government and academia held
between 2014 and 2016. To solve maintenance problems and fill
design-reality gaps in the portal, the Ministry of Planning (MPOG) joined the
University of Brasília (UnB) and the University of São Paulo (USP) to develop a
platform based on the integration and evolution of existing open-source
software, with many features and technologies novelties in the government
context.

The academic team carried out development activities in the Advanced Laboratory
of Production, Research and Innovation in Software Engineering (LAPPIS) of UnB. The
project management and development process in this laboratory is usually
executed adopting free software practices and agile approach. For this project, a total of 42 undergraduate students, two MSc
students and two coordinator-professors participated in the development team.
Six IT professionals were also hired as senior developers due their vast
experiences in Front-end/UX or in one of the softwares integrated to the
platform.

The government team was composed of a director, a coordinator, and two IT
analysts from a department of MPOG. Although it was responsible for the
execution of this collaboration project, this department generally does not
execute development of ministry's software. This department is responsible for
contracting and homologating software development services and follows
traditional management approaches, such as the RUP.

These two aforementioned teams
periodically met in person for the purpose of managing the project progress. These meetings initially only took place at the
ministry's headquarters to discuss strategic/political and technical goals.
These meetings were held monthly with the presence of two UnB professors, the
executive-secretary of the Presidency (project supporter) and all MPOG members
responsible for the project. The management of the development team was
concentrated in the academia side. The workflow was organized in Redmine in
biweekly sprints and 4-month releases, with intermediate deliveries hosted in
university environment. However, with the progress of the project, this format
proved to be inefficient. Conflicts between the internal management processes
and differences in pace and goals of each institution were compromising the
platform development.

\subsection{Survey}

We divided the UnB development team into two groups of respondents according to
their roles during the project: UnB Interns and Senior Developers. For each
group, we designed an online survey with topics related to project organization,
development process, communication and relationship between members, acquired
knowledge and experience with free software.

\begin{enumerate}
 \item \textit{UnB interns:} 42 undergraduate students who
participated in any time of the project as developer and received scholarship.
We received a total of 37 responses. Their average age is 25 years old and
91.9\% of them are male. Currently, 35.1\% continue at university as
undergraduate or graduate students, 18.9\% work as developer in a small company
and 18.9\% in medium or large companies, 10.8\% are entrepreneurs, 8.1\% are
unemployed and the others work as teachers or civil servants. 43.2\% said the
SPB project was their first experience with free software.

 \item \textit{Senior Developers:} eight advanced level researchers, MSc
students or IT market professionals who participated in some period of the
project. All of them answered the questionnaire. Their average age is 32 years
old and 87.5\% are male. They have an average of 11 years of experience in the
IT market, and currently 62.5\% of respondents are company employees, 37.5\% are
freelance developers, 25\% are master's degree students and 25\% entrepreneurs.
They have worked on average in 5 companies and participated in 4 to 80 projects.
They participated in this collaborative project between 7 to 24 months. 85.7\%
of them had some experience with free software before the SPB project.
\end{enumerate}

\subsection{Interview}

On the government side, two MPOG IT analysts were interviewed separately. They
were selected because they were the only government representatives who
interacted directly with the development team and project management process.
Each interview took an average of 2 hours with 28 open questions classified into
fours parts: Professional profile; Organization, communication and development
methodologies in the context of government and project; Satisfaction with the
developed platform; Lessons learned. They are more than 30 years old and have
been government employees for more than 7 years. Only one of them continues
working in the same ministry. For both, this collaborative project was their
first experience of government-academia development collaboration.

\subsection{Data Collection}

We quantitatively analyze data about the development of the project using data
publicly available on the SPB platform. We collect from the repository manager
of the platform, Gitlab - integrated platform software tool, all open issues
and commits made between April 2015 to February 2016 and related to the
main repository of the platform, that is, the development repositories of the
integrated software were not considered. For issues, the data collected were:
project name, author of the issue, opening date, issue title and number of
comments. We also collected informations about: total open issues, total
commits, different authors of issues, total of different authors of issues,
total of comments, authors of comments, total of authors other than comments.


% And finally, we analized Colab code before and after the project to evaluate how much effort was spent to use this software as a component of the platform.