[oss-2018] Reviewing Conclusion

Paulo Meireles
1 parent 892b9b04
Showing 1 changed file with 51 additions and 23 deletions Show diff stats
icse2018/content/06-discussion.tex
 \section{Discussion and Final Remarks}
 \label{sec:discussion}
-In this paper, we examined an empirical model used in a government-academia project, which successfully harmonized differences in their usual development approaches.
-We mapped the key decisions to improve the communication and the development process as a whole. We also designed surveys that were conducted separately for three groups
-of participants: government analysts, IT market professionals and interns. Finally,
-we collected \textit{post-mortem} public data on project management from the
-platform developed. The results revealed that nine practices were developed from three
-key decisions taken, and these practices brought 11 benefits, as summarized in the Table \ref{practices-table}.
+In this paper, we examined an empirical model used in a government-academia
+project, which successfully harmonized differences in their usual development
+approaches.  We mapped the key decisions to improve the communication and the
+development process as a whole. We designed also surveys and conducted them
+separately for three groups of participants: government analysts, IT market
+professionals, and interns. Finally, we collected \textit{post-mortem} public
+data on project management from the platform developed. The results revealed
+nine practices from three key decisions taken, and these practices brought 11
+benefits, as summarized in the Table \ref{practices-table}.
 \begin{table}[]
 \centering
@@ -60,26 +63,51 @@ bureaucratic issues involve board directors. \item Continuous Delivery
 \label{practices-table}
 \end{table}
-\textbf{RQ1.}\textit{What practices based on open source development experiences would
-help to combine teams with different management processes in a
-government-academia collaboration project?}
+Regarding to our first question,\textit{What practices based on open source
+development experiences would help to combine teams with different management
+processes in a government-academia collaboration project?}, we mapped practices
+covering aspects from communication of the project to the delivery process of
+developed code, as presented in the second column of the Table
+\ref{practices-table} (Practice Explanation).
-We mapped nine practices to reconcile the differences between government and academia in a collaborative project. These practices cover aspects from communication of the project to the delivery process of developed code, as presented in the second column of the table above (Practice Explanation).
+The results of the surveys revealed the benefits of implementing each set of
+practices for the case study, answering our second question: \textit{How do
+open source development practices benefit the process of 74 developing an
+e-government platform in a government-academia collaboration?}. The third
+column of the Table \ref{practices-table} (Benefits) shows how the practices
+adopted impacted on the relationship between members from both sides, on the
+understanding of project development process, and on the appropriation of the
+developed platform.
-\textbf{RQ2.}\textit{How do open source development practices benefit the process of
-developing an e-government platform in a government-academia collaboration?}
+The new evidences corroborate with the lessons learned that we reported in our
+previous work \cite{meirelles2017spb}, adding the point of view of the
+government and the academia in diverse performed levels. Moreover, our results
+suggest that many open source practices could be replicated in different
+contexts in which the diversity and plurality of its stakeholders need to be
+leveled and reconciled.
-The results of the surveys revealed the benefits of implementing each set of practices for the case study. The third column of the table (Benefits) shows how the practices adopted impacted on the relationship between members from both sides, on the understanding of project development process, and on the appropriation of the developed platform.
+This current work also exposed issues that were not overcome during the project
+and need to be evaluated for future government-academia collaborations for
+software development. In the interviews, MPOG analysts reported some
+difficulties during the project in understanding the idea of collaboration.
+They said they needed time to realize that the project was not client-executor
+relationship, but a partnership, and both organizations were ate the same
+hierarchical level in the work plane. They lacked the role of decision maker in
+times of deadlock and in the requirements definition. Additionally, the
+analysts reported they sometimes felt coerced by coordinators when they tried
+to communicate directly with the interns.
-The new evidences corroborate with the lessons learned and reported in our previous work \cite{meirelles2017spb}, adding the point of view of the government and the academia in diverse performed levels. Moreover, our results suggest that many open source practices could be replicated in different contexts in which the diversity and plurality of its stakeholders need to be leveled and reconciled.
+As threats to validity of this work, we can point the lack of traceable
+qualitative and quantitative records related to the first phase of the project
+(about the organization prior to the adoption of the practices mentioned above)
+and the application of surveys after project completion, depending on the
+memory of the interviewees about 30 months of the project.
-This current work also exposed issues that were not overcome during the
-project and need to be evaluated for future government-academia collaborations for software development. In the interviews, MPOG analysts reported some difficulties during the project in understanding the idea of collaboration. They said they needed time to realize that the project was not client-executor relationship, but a partnership, and both organizations were ate the same hierarchical level in the work plane. They lacked the role of decision maker in times of deadlock and in the requirements definition. Additionally, the analysts reported they sometimes felt coerced by coordinators when they tried to communicate directly with the interns.
+Finally, we have collected a lot of data that provide other analysis in the future, such as blabla, Education etc
-We consider limitations of this work to be the lack of traceable qualitative and quantitative records related to the first phase of the project (about the organization prior to the adoption of the practices mentioned above) and the application of surveys only after project completion, depending on the good memory of the interviewees about 30 months of the project.
-
-As future work, we intend to apply in another government-academia partnership
-project the practices evidenced from this case study, and conduct
-qualitative and quantitative research throughout its execution. We also intend to
-analyze the effectiveness in adopting open source practices to
-align the demands and expectations of a G-A collaboration.
+%%% Não vamos fazer isto aqui, mas sim temos a possibilidade de explorar os dados que temos em outras perpectivas com Educação etc etc (que vc sabe melhor que eu ; )
+%In the future, we intend to apply in another government-academia partnership
+%project the practices evidenced from this case study, and conduct qualitative
+%and quantitative research throughout its execution. We also intend to analyze
+%the effectiveness in adopting open source practices to align the demands and
+%expectations of a G-A collaboration.
1	\section{Discussion and Final Remarks}	1	\section{Discussion and Final Remarks}
2	\label{sec:discussion}	2	\label{sec:discussion}
3		3
4	-In this paper, we examined an empirical model used in a government-academia project, which successfully harmonized differences in their usual development approaches.
5	-We mapped the key decisions to improve the communication and the development process as a whole. We also designed surveys that were conducted separately for three groups
6	-of participants: government analysts, IT market professionals and interns. Finally,
7	-we collected \textit{post-mortem} public data on project management from the
8	-platform developed. The results revealed that nine practices were developed from three
9	-key decisions taken, and these practices brought 11 benefits, as summarized in the Table \ref{practices-table}.	4	+In this paper, we examined an empirical model used in a government-academia
		5	+project, which successfully harmonized differences in their usual development
		6	+approaches. We mapped the key decisions to improve the communication and the
		7	+development process as a whole. We designed also surveys and conducted them
		8	+separately for three groups of participants: government analysts, IT market
		9	+professionals, and interns. Finally, we collected \textit{post-mortem} public
		10	+data on project management from the platform developed. The results revealed
		11	+nine practices from three key decisions taken, and these practices brought 11
		12	+benefits, as summarized in the Table \ref{practices-table}.
10		13
11	\begin{table}[]	14	\begin{table}[]
12	\centering	15	\centering
	@@ -60,26 +63,51 @@ bureaucratic issues involve board directors. \item Continuous Delivery		@@ -60,26 +63,51 @@ bureaucratic issues involve board directors. \item Continuous Delivery
60	\label{practices-table}	63	\label{practices-table}
61	\end{table}	64	\end{table}
62		65
63	-\textbf{RQ1.}\textit{What practices based on open source development experiences would
64	-help to combine teams with different management processes in a
65	-government-academia collaboration project?}	66	+Regarding to our first question,\textit{What practices based on open source
		67	+development experiences would help to combine teams with different management
		68	+processes in a government-academia collaboration project?}, we mapped practices
		69	+covering aspects from communication of the project to the delivery process of
		70	+developed code, as presented in the second column of the Table
		71	+\ref{practices-table} (Practice Explanation).
66		72
67	-We mapped nine practices to reconcile the differences between government and academia in a collaborative project. These practices cover aspects from communication of the project to the delivery process of developed code, as presented in the second column of the table above (Practice Explanation).	73	+The results of the surveys revealed the benefits of implementing each set of
		74	+practices for the case study, answering our second question: \textit{How do
		75	+open source development practices benefit the process of 74 developing an
		76	+e-government platform in a government-academia collaboration?}. The third
		77	+column of the Table \ref{practices-table} (Benefits) shows how the practices
		78	+adopted impacted on the relationship between members from both sides, on the
		79	+understanding of project development process, and on the appropriation of the
		80	+developed platform.
68		81
69	-\textbf{RQ2.}\textit{How do open source development practices benefit the process of
70	-developing an e-government platform in a government-academia collaboration?}	82	+The new evidences corroborate with the lessons learned that we reported in our
		83	+previous work \cite{meirelles2017spb}, adding the point of view of the
		84	+government and the academia in diverse performed levels. Moreover, our results
		85	+suggest that many open source practices could be replicated in different
		86	+contexts in which the diversity and plurality of its stakeholders need to be
		87	+leveled and reconciled.
71		88
72	-The results of the surveys revealed the benefits of implementing each set of practices for the case study. The third column of the table (Benefits) shows how the practices adopted impacted on the relationship between members from both sides, on the understanding of project development process, and on the appropriation of the developed platform.	89	+This current work also exposed issues that were not overcome during the project
		90	+and need to be evaluated for future government-academia collaborations for
		91	+software development. In the interviews, MPOG analysts reported some
		92	+difficulties during the project in understanding the idea of collaboration.
		93	+They said they needed time to realize that the project was not client-executor
		94	+relationship, but a partnership, and both organizations were ate the same
		95	+hierarchical level in the work plane. They lacked the role of decision maker in
		96	+times of deadlock and in the requirements definition. Additionally, the
		97	+analysts reported they sometimes felt coerced by coordinators when they tried
		98	+to communicate directly with the interns.
73		99
74	-The new evidences corroborate with the lessons learned and reported in our previous work \cite{meirelles2017spb}, adding the point of view of the government and the academia in diverse performed levels. Moreover, our results suggest that many open source practices could be replicated in different contexts in which the diversity and plurality of its stakeholders need to be leveled and reconciled.	100	+As threats to validity of this work, we can point the lack of traceable
		101	+qualitative and quantitative records related to the first phase of the project
		102	+(about the organization prior to the adoption of the practices mentioned above)
		103	+and the application of surveys after project completion, depending on the
		104	+memory of the interviewees about 30 months of the project.
75		105
76	-This current work also exposed issues that were not overcome during the
77	-project and need to be evaluated for future government-academia collaborations for software development. In the interviews, MPOG analysts reported some difficulties during the project in understanding the idea of collaboration. They said they needed time to realize that the project was not client-executor relationship, but a partnership, and both organizations were ate the same hierarchical level in the work plane. They lacked the role of decision maker in times of deadlock and in the requirements definition. Additionally, the analysts reported they sometimes felt coerced by coordinators when they tried to communicate directly with the interns.	106	+Finally, we have collected a lot of data that provide other analysis in the future, such as blabla, Education etc
78		107
79	-We consider limitations of this work to be the lack of traceable qualitative and quantitative records related to the first phase of the project (about the organization prior to the adoption of the practices mentioned above) and the application of surveys only after project completion, depending on the good memory of the interviewees about 30 months of the project.
80	-
81	-As future work, we intend to apply in another government-academia partnership
82	-project the practices evidenced from this case study, and conduct
83	-qualitative and quantitative research throughout its execution. We also intend to
84	-analyze the effectiveness in adopting open source practices to
85	-align the demands and expectations of a G-A collaboration.	108	+%%% Não vamos fazer isto aqui, mas sim temos a possibilidade de explorar os dados que temos em outras perpectivas com Educação etc etc (que vc sabe melhor que eu ; )
		109	+%In the future, we intend to apply in another government-academia partnership
		110	+%project the practices evidenced from this case study, and conduct qualitative
		111	+%and quantitative research throughout its execution. We also intend to analyze
		112	+%the effectiveness in adopting open source practices to align the demands and
		113	+%expectations of a G-A collaboration.