06-conclusion.tex 2.36 KB
\section{Conclusion}
\label{sec:conclusion}

Organizational culture is built and reinforced every life year of a large-size
organization. These cultural values reflect on the internal management
processes and the norms of communication among its members. In the context of
software development projects, each institution adopts development methods that
best meet its managerial procedures and organizational routines. When two
large-size organizations decide to develop a solution collaboratively, the
development methods and workflow of one may conflict with the interests of the
other. In a case of government-academia collaboration, conciliating their
different management processes is crucial, since the poor and unadaptable
management could lead the project to fail, resulting in the waste of
population-funded resources.

In this study, we investigated the management method employed at the SPB portal
project, a partnership between the Brazilian government and universities. As a
result, we identified a set of FLOSS and agile best practices, empirically
employed by the development leaders, which improved the workflow and
relationship between the organizations involved.
 
Regarding our first research question \textit{``How to introduce FLOSS and
agile best practices into government-academia collaboration projects?''}, we
examined the SPB project and identified three macro-decisions taken by the
academic coordinators that drove them to intuitively and unsystematically adopt
nine FLOSS and agile best practices in the development process.

The interviewed responses allowed us to understand how FLOSS and agile
practices have benefited the people and project management. Based on that, we
answered our second research question \textit{``What practices favor effective
team management in government-academia collaborative projects?''}, making to
explicit 14 benefits obtained from the use of the nine best practices, all
presented in Table \ref{practices-table}.

Finally, we collected a significant amount of data and testimonials related to
the teaching of software engineering. We consider the studied project an
educational case, an example of teaching FLOSS and agile techniques applied to
real-world software development. As future work, we intend to analyze this
collected information to propose improvements in education methodologies of
software engineering undergraduate students as well.