Commit adeed3dd31d29bd0e0372c945f5b29bf7e0d3202
1 parent
36cf63b3
Exists in
master
and in
3 other branches
[oss-2018] applying Paulos suggestions on research design and small fixes on discussion
Showing
2 changed files
with
58 additions
and
59 deletions
Show diff stats
icse2018/content/04-methods.tex
1 | \section{Research Design} | 1 | \section{Research Design} |
2 | \label{sec:researchdesign} | 2 | \label{sec:researchdesign} |
3 | 3 | ||
4 | -Our analysis was guided by the following research questions: | 4 | +The focus on this paper is finding practical ways to reconcile cultural |
5 | +differences in software development between academia and government, | ||
6 | +without modifying their internal processes. Our analysis was guided by the | ||
7 | +following research questions: | ||
5 | 8 | ||
6 | \textbf{RQ1.}{What practices based on open source development experiences would | 9 | \textbf{RQ1.}{What practices based on open source development experiences would |
7 | help to combine teams with different management processes in a | 10 | help to combine teams with different management processes in a |
@@ -13,11 +16,11 @@ developing an e-government platform in a government-academia collaboration?} | @@ -13,11 +16,11 @@ developing an e-government platform in a government-academia collaboration?} | ||
13 | 16 | ||
14 | To answer these questions, we use as a case study the evolution project of the | 17 | To answer these questions, we use as a case study the evolution project of the |
15 | SPB portal \cite{meirelles2017spb}, a government and academia collaborative | 18 | SPB portal \cite{meirelles2017spb}, a government and academia collaborative |
16 | -development based on open source software integration. From this project, we | ||
17 | -collect public data from the project development environment available on the | ||
18 | -developed platform itself, and conduct two surveys and an interview aimed at the | ||
19 | -different roles performed by the ex-project participants, as detailed in the | ||
20 | -following subsections | 19 | +development based on open source software integration. We designed two surveys |
20 | +and an interview aimed at the different roles performed by the ex-project | ||
21 | +participants and collect public data from the project development environment | ||
22 | +available on the developed platform itself. Our research approach is detailed | ||
23 | +in the following subsections. | ||
21 | 24 | ||
22 | \subsection{The case estudy} | 25 | \subsection{The case estudy} |
23 | 26 | ||
@@ -31,13 +34,13 @@ software, with many features and technologies novelties in the government | @@ -31,13 +34,13 @@ software, with many features and technologies novelties in the government | ||
31 | context. | 34 | context. |
32 | 35 | ||
33 | The academic team carried out development activities in the Advanced Laboratory | 36 | The academic team carried out development activities in the Advanced Laboratory |
34 | -of Production, Research and Innovation in Software Engineering (LAPPIS) of UnB. The | ||
35 | -project management and development process in this laboratory is usually | ||
36 | -executed adopting free software practices and agile approach. For this project, a total of 42 undergraduate students, two MSc | ||
37 | -students and two coordinator-professors participated in the development team. | ||
38 | -Six IT professionals were also hired as senior developers due their vast | ||
39 | -experiences in Front-end/UX or in one of the softwares integrated to the | ||
40 | -platform. | 37 | +of Production, Research and Innovation in Software Engineering (LAPPIS) of UnB. |
38 | +The project management and development process in this laboratory is usually | ||
39 | +executed adopting free software practices and agile approach. For this project, | ||
40 | +a total of 42 undergraduate students, two MSc students and two | ||
41 | +coordinator-professors participated in the development team. Six IT | ||
42 | +professionals were also hired as senior developers due their vast experiences in | ||
43 | +Front-end/UX or in one of the softwares integrated to the platform. | ||
41 | 44 | ||
42 | The government team was composed of a director, a coordinator, and two IT | 45 | The government team was composed of a director, a coordinator, and two IT |
43 | analysts from a department of MPOG. Although it was responsible for the | 46 | analysts from a department of MPOG. Although it was responsible for the |
@@ -46,8 +49,8 @@ execute development of ministry's software. This department is responsible for | @@ -46,8 +49,8 @@ execute development of ministry's software. This department is responsible for | ||
46 | contracting and homologating software development services and follows | 49 | contracting and homologating software development services and follows |
47 | traditional management approaches, such as the RUP. | 50 | traditional management approaches, such as the RUP. |
48 | 51 | ||
49 | -These two aforementioned teams | ||
50 | -periodically met in person for the purpose of managing the project progress. These meetings initially only took place at the | 52 | +These two aforementioned teams periodically met in person for the purpose of |
53 | +managing the project progress. These meetings initially only took place at the | ||
51 | ministry's headquarters to discuss strategic/political and technical goals. | 54 | ministry's headquarters to discuss strategic/political and technical goals. |
52 | These meetings were held monthly with the presence of two UnB professors, the | 55 | These meetings were held monthly with the presence of two UnB professors, the |
53 | executive-secretary of the Presidency (project supporter) and all MPOG members | 56 | executive-secretary of the Presidency (project supporter) and all MPOG members |
@@ -59,52 +62,51 @@ proved to be inefficient. Conflicts between the internal management processes | @@ -59,52 +62,51 @@ proved to be inefficient. Conflicts between the internal management processes | ||
59 | and differences in pace and goals of each institution were compromising the | 62 | and differences in pace and goals of each institution were compromising the |
60 | platform development. | 63 | platform development. |
61 | 64 | ||
62 | -\subsection{Survey} | 65 | +\subsection{Survey and data collection} |
63 | 66 | ||
64 | We divided the UnB development team into two groups of respondents according to | 67 | We divided the UnB development team into two groups of respondents according to |
65 | their roles during the project: UnB Interns and Senior Developers. For each | 68 | their roles during the project: UnB Interns and Senior Developers. For each |
66 | group, we designed an online survey with topics related to project organization, | 69 | group, we designed an online survey with topics related to project organization, |
67 | development process, communication and relationship between members, acquired | 70 | development process, communication and relationship between members, acquired |
68 | -knowledge and experience with free software. | 71 | +knowledge and experience with free software. We also interviewed two MPOG |
72 | +analysts who directly interacted with the development team and project | ||
73 | +development process. The interview questions could be classified into four | ||
74 | +parts: Professional profile; Organization, communication and development | ||
75 | +methodologies in the context of government and project; Satisfaction with the | ||
76 | +developed platform; Lessons learned. | ||
69 | 77 | ||
70 | \begin{enumerate} | 78 | \begin{enumerate} |
71 | - \item \textit{UnB interns:} 42 undergraduate students who | ||
72 | -participated in any time of the project as developer and received scholarship. | ||
73 | -We received a total of 37 responses. Their average age is 25 years old and | ||
74 | -91.9\% of them are male. Currently, 35.1\% continue at university as | ||
75 | -undergraduate or graduate students, 18.9\% work as developer in a small company | ||
76 | -and 18.9\% in medium or large companies, 10.8\% are entrepreneurs, 8.1\% are | ||
77 | -unemployed and the others work as teachers or civil servants. 43.2\% said the | ||
78 | -SPB project was their first experience with free software. | ||
79 | - | ||
80 | - \item \textit{Senior Developers:} eight advanced level researchers, MSc | ||
81 | -students or IT market professionals who participated in some period of the | ||
82 | -project. All of them answered the questionnaire. Their average age is 32 years | ||
83 | -old and 87.5\% are male. They have an average of 11 years of experience in the | ||
84 | -IT market, and currently 62.5\% of respondents are company employees, 37.5\% are | ||
85 | -freelance developers, 25\% are master's degree students and 25\% entrepreneurs. | ||
86 | -They have worked on average in 5 companies and participated in 4 to 80 projects. | ||
87 | -They participated in this collaborative project between 7 to 24 months. 85.7\% | ||
88 | -of them had some experience with free software before the SPB project. | 79 | + \item \textit{UnB interns:} We sent the link of the online survey through |
80 | +emails to 42 undergraduate students who participated in any time of the project | ||
81 | +as developer receiving scholarship. We received a total of 37 responses. Their | ||
82 | +average age is 25 years old and 91.9\% of them are male. Currently, 35.1\% | ||
83 | +continue at university as undergraduate or graduate students, 18.9\% work as | ||
84 | +developer in a small company and 18.9\% in medium or large companies, 10.8\% are | ||
85 | +entrepreneurs, 8.1\% are unemployed and the others work as teachers or civil | ||
86 | +servants. 43.2\% said the SPB project was their first experience with free | ||
87 | +software. | ||
88 | + | ||
89 | + \item \textit{Senior Developers:} We also sent the link of the online survey | ||
90 | +through emails to eight advanced level researchers (MSc students or IT market | ||
91 | +professionals who participated in some period of the project). All of them | ||
92 | +answered the questionnaire. Their average age is 32 years old and 87.5\% are | ||
93 | +male. They have an average of 11 years of experience in the IT market, and | ||
94 | +currently 62.5\% of respondents are company employees, 37.5\% are freelance | ||
95 | +developers, 25\% are master's degree students and 25\% entrepreneurs. They have | ||
96 | +worked on average in 5 companies and participated in 4 to 80 projects. They | ||
97 | +participated in this collaborative project between 7 to 24 months. 85.7\% of | ||
98 | +them had some experience with free software before the SPB project. | ||
99 | + | ||
100 | + \item \textit{MPOG Analysts:} two MPOG IT analysts were interviewed separately. | ||
101 | +Each interview took an average of 2 hours with 28 open questions. They are more | ||
102 | +than 30 years old and have been government employees for more than 7 years. | ||
103 | +Only one of them continues working in the same ministry. For both, this | ||
104 | +collaborative project was their first experience of government-academia | ||
105 | +development collaboration. | ||
89 | \end{enumerate} | 106 | \end{enumerate} |
90 | 107 | ||
91 | -\subsection{Interview} | ||
92 | - | ||
93 | -On the government side, two MPOG IT analysts were interviewed separately. They | ||
94 | -were selected because they were the only government representatives who | ||
95 | -interacted directly with the development team and project management process. | ||
96 | -Each interview took an average of 2 hours with 28 open questions classified into | ||
97 | -fours parts: Professional profile; Organization, communication and development | ||
98 | -methodologies in the context of government and project; Satisfaction with the | ||
99 | -developed platform; Lessons learned. They are more than 30 years old and have | ||
100 | -been government employees for more than 7 years. Only one of them continues | ||
101 | -working in the same ministry. For both, this collaborative project was their | ||
102 | -first experience of government-academia development collaboration. | ||
103 | - | ||
104 | -\subsection{Data Collection} | ||
105 | - | ||
106 | -We quantitatively analyze data about the development of the project using data | ||
107 | -publicly available on the SPB platform. We collect from the repository manager | 108 | +Finally, we quantitatively analyze data about the development of the project, |
109 | +publicly available on the SPB platform. We collected from the repository manager | ||
108 | of the platform, Gitlab - integrated platform software tool, all open issues | 110 | of the platform, Gitlab - integrated platform software tool, all open issues |
109 | and commits made between April 2015 to February 2016 and related to the | 111 | and commits made between April 2015 to February 2016 and related to the |
110 | main repository of the platform, that is, the development repositories of the | 112 | main repository of the platform, that is, the development repositories of the |
@@ -113,6 +115,3 @@ project name, author of the issue, opening date, issue title and number of | @@ -113,6 +115,3 @@ project name, author of the issue, opening date, issue title and number of | ||
113 | comments. We also collected informations about: total open issues, total | 115 | comments. We also collected informations about: total open issues, total |
114 | commits, different authors of issues, total of different authors of issues, | 116 | commits, different authors of issues, total of different authors of issues, |
115 | total of comments, authors of comments, total of authors other than comments. | 117 | total of comments, authors of comments, total of authors other than comments. |
116 | - | ||
117 | - | ||
118 | -% 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. |
icse2018/content/06-discussion.tex
@@ -46,10 +46,10 @@ the coordinator responded. So that was negative, because we felt a little | @@ -46,10 +46,10 @@ the coordinator responded. So that was negative, because we felt a little | ||
46 | coerced from talking directly to the teams"} | 46 | coerced from talking directly to the teams"} |
47 | \end {itemize} | 47 | \end {itemize} |
48 | 48 | ||
49 | -As future work, we will reapply in another government-academia paternship | ||
50 | -project the practices evidenced in this case study, and conduct | ||
51 | -qualitative and quantitative research throughout its execution. We intend to | ||
52 | -prove the effectiveness in adopting free software development practices to | 49 | +As future work, we intend to reapply in another government-academia paternship |
50 | +project the practices evidenced from this case study, and conduct | ||
51 | +qualitative and quantitative research throughout its execution. We also intend to | ||
52 | +analyze the effectiveness in adopting free software development practices to | ||
53 | align the demands and expectations of a G-A collaboration. | 53 | align the demands and expectations of a G-A collaboration. |
54 | 54 | ||
55 | \begin{comment} | 55 | \begin{comment} |