06-conclusion.tex 2.65 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 work, we investigated the management method employed at the SPB project,
a partnership between the Brazilian Ministry of Planning, the University of
Brasília and the University of São Paulo. This method was empirically built
using OSS and agile development references. As a result of this study, we
identified a set of best practices which improves the workflow and
relationship between the organizations involved. 
 
Regarding our first research question \textit{How to introduce open source and
agile best practices into government-academia collaboration project?} we
examined the SPB project and identified three macro-decisions taken by the
academic coordinators that led them to intuitively and non-systematically adopt
agile and open source practices in the development process. We extracted nine
best management practices and verified their effective use collecting data from
the management tool and interviewing the project participants.

The interviewed responses allowed us to understand how OSS and agile practices
have benefited the people and project management. Considering the evidence found, we
answered our second research question \textit{What practices would favor
effective team management in government-academia collaborative project?}. As a
result, we listed in Table \ref{practices-table} eleven benefits obtained from
the use of the nine practices aforementioned.

Finally, we collected a significant amount of data and testimonials related to
the teaching of software engineering. We consider that the project studied is
also an educational case, it is an example of how to teach information
technology students agile and open source methodologies applied to
production-level software development. As future work, we intend to analyze this
collected information to propose improvements in the teaching of software
engineering for undergraduates.