\section{Introduction}

E-government projects differ from others due to their complexity and extension
\cite{anthopoulos2016egovernment}. They are complex because they combine
construction, innovation, information \& communications technologies, politics,
and social impact. Their extension, on the other hand, is related to their scope,
target audience, organizational size, time, and the corresponding resistance to
change. Government-academia collaborative projects can be considered an
alternative to create novelty for e-government projects and to meet the needs of
society.  This collaborative work has challenges, such as organizing the
collaboration project, aligning goals, synchronizing the pace of between
government and academia \cite{anthopoulos2016egovernment}, and overcoming the
failure trend of e-government projects \cite{goldfinch2007pessimism}.

Poor project management is one of the main reasons why e-government projects
fail \cite{anthopoulos2016egovernment}. When government and academia combine
efforts to develop an e-government solution, the differences in the project
management become an issue. Academia commonly work on cutting edge of
technology while government is still relying on traditional techniques.
Changing the development process in large-size institutions represents
an organizational disturbance which impacts on structure, culture, and
management practices \cite{nerur2015challenges}. As a result, government and
academia have to harmonize their view to increasing the chances of success in
projects with tight deadlines and short budgets.

% TODO: Projetos de sl tem x características e muitas de suas práticas tem se mostrado válidas e que  abrem precedentes para utilizar no contexto governo academia. Falar da influência do SL no projeto

In this work we investigate a set of practices from a 30-month
government-academia project that helped to harmonize the differences between
government and academia management cultures. We trace the best practices based
on open source ecosystems and agile methodologies. Finally, we validate their
benefits by collecting data from the main project repository and by surveying
the project participant points of view.

