\section{Related work}
\label{sec:relatedwork}

% TODO: Verificar se não vale a pena citar os fatores que o Strode descobriu.
% Eu acho que deixaria a frase mais completa
Discussions on how to introduce new management methods into an organization are
present in several papers.  Nerur et al. recognized critical issues concerning
the migration from traditional to agile by comparing practices of both
methodologies \cite{nerur2015challenges}. The authors point out managerial,
organizational, people, process, and technological issues to be rethought and
reconfigured in an organization for a successful migration. Strode et al.
investigated the relationship between the adoption of agile methodologies and
organizational culture \cite{impactOfOrganizationalCulture} by evaluating nine
projects. They identified a set of factors directly linked to the agile
methods.

Some works also discuss how academia can collaborate with the industry in the
management of software projects. Chookittikul et al. evaluated the increasing
use of the agile techniques in the software development companies in Thailand.
The authors suggested that universities should create curricula which develop
in their undergraduate student's practical skills required by industry (mainly
agile practices) to promote growth in the local software business \cite{cho2011gap}.
Sandberg et al. report the use of Scrum in a collaborative research consortium
between industry and academia (involving ten industry partners and five
universities in Sweden) \cite{sandberg2017iacollaboration}.

Complex and large-scale organizations, such as the public administration, have
to deal with multiple project variables. Alleman et al. describe a production
deployment for the US government, focus on the methodology applied to address
long-term planning and value estimation \cite{alleman2003making}.  Agile
methods application in the Brazilian public sector are approached by Melo et
al. \cite{melo2013agileBr} and De Sousa et al. \cite{de2016using}, both are
experiences limited to pilot projects.

Several works tried to highlight the FLOSS practices, while others attempted to
determine the relationship between the FLOSS practices and agile methods.
Capiluppi et al. examined about 400 projects to find FLOSS project properties
\cite{capiluppi}. In their work, they extracted generic characterization
(project size, age, license, and programming language), analyzed the average
number of people involved in the project, the community of user, and
documentation characteristics. Warsta et al. found differences and similarities
between agile development and FLOSS practices \cite{warsta}. The authors argued
that FLOSS development may differ from agile by philosophical and economic
perspective, on the other hand, both shares the definition of work. Finally,
Eric Raymond describes many of his experience and decisions in his work with
FLOSS communities \cite{raymond}, this report has many intersections with the
agile manifesto.

This paper distinguishes itself from others by studying a a production level
software development collaboration between government and academia. We extracted
empirical practices that helped to harmonize the interactions between two
different development process and satisfied the management process of both
sides. We analyzed these methods from the FLOSS an agile perspective.