Commit 22ed8dc0f40c0775b350f50e14ea64b53b3a2608

Authored by Melissa Wen
1 parent 3c84d052

[oss-2018] Research Design

icse2018/content/04-case.tex
@@ -9,7 +9,7 @@ The academic team carried out development activities in the Advanced Laboratory @@ -9,7 +9,7 @@ The academic team carried out development activities in the Advanced Laboratory
9 of Production, Research and Innovation in Software Engineering of UnB. The 9 of Production, Research and Innovation in Software Engineering of UnB. The
10 project management and development process in this laboratory is usually 10 project management and development process in this laboratory is usually
11 executed adopting agile methodologies, such as Extreme Programming (XP), Scrum 11 executed adopting agile methodologies, such as Extreme Programming (XP), Scrum
12 -and Kanban. For this project, a total of 42 undergraduate students, two master's 12 +and Kanban. For this project, a total of 42 undergraduate students, two MSc
13 students and two coordinator-professors participated in the development team. 13 students and two coordinator-professors participated in the development team.
14 Six IT professionals were also hired as senior developers due their vast 14 Six IT professionals were also hired as senior developers due their vast
15 experiences in Front-end/UX or in one of the softwares integrated to the 15 experiences in Front-end/UX or in one of the softwares integrated to the
icse2018/content/05-methods.tex
1 \section{Research Design} 1 \section{Research Design}
2 \label{sec:researchdesign} 2 \label{sec:researchdesign}
3 3
4 -In this article we use the SPB project \cite{meirelles2017spb} case to analyze  
5 -practical methods of project management and software development and to  
6 -validate which techniques were efficient to overcome the differences and  
7 -difficulties existing in a consortium between government and university. In  
8 -addition to known variables in a research collaboration between industry and  
9 -academia \cite{sandberg2017iacollaboration}, this case study also presents  
10 -typical characteristics of e-government projects: complexity in terms of  
11 -organizational size, corresponding resistance to change, political bias and  
12 -end-users' impact \cite{anthopoulos2016government}. The study of how these  
13 -factors led to adaptations and changes in organization within the project and  
14 -how differences in development process were overcome was guided by the  
15 -following research questions:  
16 -  
17 -  
18 -\textbf{Q1.} \textit{Can teams with distinct software development processes be well combined in the same project?}  
19 -%TODO: explicar/descrever a questão  
20 -  
21 -\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?}  
22 -%TODO: explicar/descrever a questão  
23 -  
24 -  
25 -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: 4 +To answer the two research questions presented in the previous section, we
  5 +conducted after-project surveys divided into three target groups of project
  6 +participants:
26 7
27 \begin{enumerate} 8 \begin{enumerate}
28 - \item \textit{sending a questionnaire to all students}  
29 - \item \textit{sending an open questionnaire to IT professionals}  
30 - \item \textit{interviewing government representatives involved in the project.}  
31 - \end{enumerate}  
32 -  
33 -(Describe questionnaires and interviews)  
34 -  
35 -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.  
36 -  
37 -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. 9 + \item \textit{MPOG Staff:} two government-side employees who have acted
  10 +directly in the platform development process. They were separately interviewed
  11 +by videoconference using the Hangouts platform. The interviews took an average
  12 +of 2 hours with 28 open questions divided by subject: Professional profile;
  13 +Organization, communication and development methodologies in the context of
  14 +government and project; Satisfaction with the developed platform; Lessons
  15 +learned.
  16 + \item \textit{UnB students-developers:} 42 undergraduate students who
  17 +participated in any time of the project receiving scholarship. A
  18 +questionnaire with 45 closed and six open questions was sent through emails using
  19 +the Google Forms platform. The topics covered were: Organization, communication
  20 +and development activities between the respondents and the different groups of
  21 +the project; Learning acquired; Professional learning; Experience with FLOSS
  22 +projects. We received a total of 37 responses.
  23 + \item \textit{Senior Developers:} eight advanced level researchers, MSc students or
  24 +IT market professionals who participated in some period of the project. A
  25 +questionnaire with 29 closed questions and 10 open questions addressed the
  26 +follow topics: Organization, communication and relationship between respondents
  27 +and distinct groups of the project; Development process; Experience with Free
  28 +Software. All eight recipients answered the questions.
  29 +\end{enumerate}
  30 +
  31 +In a second round, we also collect post-mortem data from Redmine
  32 +(outside the SPB portal), Gitlab and Mailman (inside the SPB portal) - tools
  33 +used for management, communication and code versioning during the 30-month
  34 +project. The data of the tools provided by the SPB portal are open and available
  35 +for access at any time. For Redmine, we use a backup and instantiate the tool on
  36 +a server in UnB's research lab. The analysis of these data composes and ratifies
  37 +the evidences obtained in the previous round (surveys). The information obtained
  38 +represents, in terms of volume, interactions and the evolution of these
  39 +interactions between the government and academia teams, and, in terms of
  40 +development complexity, the platform size and quantity of software releases
  41 +delivered.
  42 +
  43 +
  44 +%Ambas possuem nível superior na área de TI e são funcionárias do governo a mais de 7 anos. Apenas uma delas segue atuando no mesmo ministério.
  45 +%Para o segundo grupo, um formulário online foi enviado aos 42 alunos e ex-alunos do curso de engenharia de software da UnB que participaram do projeto como bolsistas. A idade média dos 37 respondentes é de 25 anos e 91,9\% deles são do sexo masculino. Atualmente, 35,1\% seguem na universidade como alunos de graduação ou pós-graduação, 18,9\% atuam como desenvolvedor em empresa de pequeno porte e 18,9\% em empresas de médio ou grande porte, 10,8\% são empreendedores, 8,1\% estão desempregados e os demais atuam como professor ou funcionário público.
  46 +%O terceiro grupo é formado por 8 profissionais do mercado de TI ou alunos de mestrado (no período do projeto). Todos responderam ao formulário online enviado. As idades média é de 32 anos e 87,5\% são do sexo masculino. Eles possuem em média 11 anos de experiência no mercado de TI, e atualmente 25\% são estudantes de mestrado, 25\% empreendedores, 37,5\% são desenvolvedores freelancer e 62,5\% dos respondentes são funcionários de empresa. Já trabalharam em média em 5 empresas e participaram de 4 a 80 projetos. Eles participaram do projeto de colaboração estudado entre 7 a 24 meses.
  47 +
  48 +% 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.