[oss-2018] improvements on discussion and conclusion sections

Melissa Wen
1 parent 660a29db
Showing 2 changed files with 45 additions and 44 deletions Show diff stats
oss2018/content/05-discussion.tex
oss2018/content/06-conclusion.tex
@@ -67,32 +67,30 @@ table \cite{practices-table}
 The results of this current work corroborate the lessons learned in our previous
 work on studying the SPB project case \cite{meirelles2017spb}. Evidence from the
-data collected and responses of questionnaires and interviews reinforces what
-has been reported by the academic coordination of the project, adding point of
-views of government and other roles involved on the academic side. In this work,
-the new evidence also reveals conflicts not overcame during the project and that
+data collected and responses to questionnaires and interviews reinforce what
+has been reported by the academic coordination of the project, adding the point of
+views of government and other roles involved on the academic side. The
+respondents also reveal conflicts not overcame during the project that
 should be evaluated for future software development partnerships between
 government and academia. Among the problems faced, the government staff had
-difficult to understand how collaboration works, that is, they took a time to
+difficulty to understand how collaboration works, that is, they took time to
 realize that the project was not a client-executor relationship and that both
 organizations were at the same hierarchical level in the work plan. They also
 felt the project needed a decision-maker role to resolve impasses between
 organizations. Finally, they said that at times they felt intimidated by the
 coordinator in some attempts to communicate directly with the UnB interns.
-\textit{Limitations}. We consider that the results found in this work are valid
+\textit{Limitations}. We consider the results found in this work are valid
 for the project studied, but may not have the same effectiveness for another
 government-academia collaboration. However, based on the benefits presented in
 the Table \ref{practices-table}, we believe that the abovementioned practices
 and other OSS practices should be evaluated and used in contexts with plurality
-and diversity of stakeholders, such as collaborations. 
-
-As threats to the validity of this work, we point out the lack of
-communication records and lack of treceability of the management data referring
-to the first phase of the project. We also consider as a threat the hiatus
-between the completion of the project and the conduction of interviews and
-questionnaires with the former team members, since we rely on the memory of the
-interviewees to rescue the events. Also, the new work experiences of the
-respondents after the project and their current working mindset may also modify
-their interpretation of the topics addressed in the questionnaire and
-consequently their responses.
+and diversity of stakeholders, such as collaborations. As threats to the
+validity of this work, we point out the lack of communication records and low
+traceability of the management data referring to the first phase of the
+project. We also consider as a threat the hiatus between the completion of the
+project and the conduction of interviews and questionnaires, since we rely on
+the memory of the interviewees to rescue the events. Also, the new work
+experiences of the respondents after the project and their current working
+mindset may also modify their interpretation of the topics addressed in the
+questionnaire and consequently their responses.
+\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 in the norms of communication among its members. In the context of software
+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 management
-methods and workflow of one may conflict with the interests of the other. This
-problem becomes crucial when it involves collaboration between government and
-academia. The poor and unadaptable management could lead the project to fail,
-resulting in a waste of population-funded resources.
+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 study, we investigated the SPB project, a collaborative project between
-the Brazilian Ministry of Planning and two Brazilian universities, the
-University of Brasília and the University of São Paulo. In this project, the
-coordinators, advised by IT market developers, used management and communication
-practices from OSS projects to improve the workflow and relationship between the
-organizations involved. 
+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
+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.
-Analyzing the interview responses we can understand how OSS and agile practices
-have benefited people and project management. Considering the evidence found, we
-answered our second research question, \textit{What practices would favor
+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 eleven benefits obtained from the use of the nine practices
-aforementioned.
+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 in this work
-related to the teaching of software engineering. We consider that the project
-studied is also an educational case. The SPB project 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. 
+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.