Software Público Brasileiro

\section{Introduction}

%Falar sobre unir tradicional (guiado por tarefas e atividades) e agil (guiado por funcionalidades) - nerur et al
%Falar sobre mudanças estrutura organizacional organica (agil) e burocratica (tradicional)

Several development processes were introduced with the intention to increase
the chances of success in software projects, the traditional and agile methods
are the most popular. The former is a process-centric based on the belief that
variation on the project can be detected in advance, consequently, it is
possible to control the project by continuous measure and
refine\cite{agileSoftwareDevelopment}. Latter is based on the belief that
project is unpredictable, hence, it centered on small interaction. The agile
method has shown a great increase in productivity
\cite{onTheProductivityOfAgile, anAnalysisOfTrends}, as a result, many
researchers investigate how to make the transition from traditional to agile.
In this work, we demonstrated a less abrupt approach in which we tried to
harmonize different processes in the same project.

The traditional method has been used for a long time as a way to discipline the
software development process. This methodology can be characterized by the
predictive approach, focus on documentation, processes oriented, and heavy
based on tools\cite{comparisonAgileTraditional}. The agile method, on the other
hand, embraces the adaptative approach. It is characterized by the
people-oriented approach \cite{agileSoftwareDevelopment}, the collaboration
with clients \cite{theNewMethodology}, small self-organized teams
\cite{peopleFactor}, and the flexibility regarding planning
\cite{agileSoftwareDevelopmentEco}. In a nutshell, both methodologies intend to
increase the chance of the project success. Organizations like governments,
already absorb the traditional methodology as a part of its own culture. This
situation may produce tensions when two or more development teams with
different methodology have to collaborate [?].

%TODO: Achar ref para a última linha

As the agile methodology became popular, some researchers demonstrated an
increase in the software production due to this methodology
\cite{onTheProductivityOfAgile, anAnalysisOfTrends}.  Additionally, companies
and organizations became interested to migrate from traditional to the agile
approach. However, the transition from traditional to agile is not an easy task
and have to deal with challenges related to people, process, management, and
technology\cite{challengesOfMigrating}. The organization culture is another
important factor to be considered for adopting agile
methodology\cite{impactOfOrganizationalCulture}. Finally, when we bring those
challenges and organizational barriers to the government context the situation
became more challenge.

In this paper, we present practices used to harmonize different processes in
the same project. In our previous work\cite{}, we reported the lessons learned
in a project with a Brazilian government.
% Fazer o gancho para a questão da academia e industria
% Abordar a questão do governo brasileiro e do fato da UnB estar na capital do país
% Não estamos falando em sucesso do projeto, mas no sucesso do desenvolvimento, comunicação e interação com o governo
% Falar que no caso de Brasília, o governo é o principal/mais forte cliente da região e estar bem preparado para entender as peculiaridades deste tipo de cliente é importante para os alunos profissionalmente.


% TODO: Verificar as seções
Section \ref{sec:relatedwork} discuss the related work on blablabla. Section \ref{sec:casestudy} presents blablabla. Section
\ref{sec:researchdesign} describes our research questions and methodology.
Section \ref{sec:discussion} presents findings derived from our quantitative
and qualitative analyses. Section \ref{sec:results} we describe the results.
Finally, we present the limitations, related work and conclusions.