Software Público Brasileiro

\section{Research Design}
\label{sec:researchdesign}

In this article we use the SPB project \cite{meirelles2017spb} case to analyze practical methods of project management and software development and to validate which techniques were efficient to overcome the differences and difficulties existing in a consortium between government and university. In addition to known variables in a research collaboration between industry and academia \cite{sandberg2017iacollaboration}, this case study also presents typical characteristics of e-government projects: complexity in terms of organizational size, corresponding resistance to change, political bias and end-users' impact \cite{anthopoulos2016government}. 

The study of how these factors led to adaptations and changes in organization within the project and how differences in development process were overcome was guided by the following research questions:
%


\textbf{Q1.} \textit{Can teams with distinct software development processes be well combined in the same project?}
%


\textbf{Q2.} \textit{Which boundaries should be established between the administrative concern of organizations involved in a project and the management of the development team?}


To answer these questions, we conducted a survey to explore how each group of project participants viewed the platform development process, how these groups interacted with each other, what difficulties were encountered in these interactions, and how conflicts impacted their activities. The survey was divided into three parts:

\begin{enumerate}
  \item \textit{sending a questionnaire to all students}
  \item \textit{sending an open questionnaire to IT professionals}
  \item \textit{interviewing government representatives involved in the project.}
 \end{enumerate}

(Describe questionnaires and interviews)

We also analized data from Redmine and Gitlab, tools used for management and communication during the project, as well as messages on the project's mailing list.

And finally, we analized Colab code before and after the project to evaluate how much effort was spent to use this software as a component of the platform.