Releated works (in progress) and text reviews

Melissa Wen
1 parent e0768bea
Showing 7 changed files with 156 additions and 27 deletions Show diff stats
icse2018/bibliography.bib
icse2018/content/02-related_work.tex
icse2018/content/03-context.tex
icse2018/content/05-methods.tex
icse2018/content/06-results.tex
icse2018/content/09-acknowledgements.tex
icse2018/spb-icse-seip.tex
@@ -75,3 +75,77 @@
   organization={IEEE}
 }
  
+@inproceedings{sandberg2017iacollaboration,
+ author = {Sandberg, Anna B\"{o}rjesson and Crnkovic, Ivica},
+ title = {Meeting Industry: Academia Research Collaboration Challenges with Agile Methodologies},
+ booktitle = {Proceedings of the 39th International Conference on Software Engineering: Software Engineering in Practice Track},
+ series = {ICSE-SEIP '17},
+ year = {2017},
+ isbn = {978-1-5386-2717-4},
+ location = {Buenos Aires, Argentina},
+ pages = {73--82},
+ numpages = {10},
+ url = {https://doi.org/10.1109/ICSE-SEIP.2017.20},
+ doi = {10.1109/ICSE-SEIP.2017.20},
+ acmid = {3103122},
+ publisher = {IEEE Press},
+ address = {Piscataway, NJ, USA},
+ keywords = {agile methodologies, case study, collaboration, industry-academia research}
+}
+
+@inproceedings{meirelles2017spb,
+ author = {Meirelles, Paulo and Wen, Melissa and Terceiro, Antonio and Siqueira, Rodrigo and Kanashiro, Lucas and Neri, Hilmer},
+ title = {Brazilian Public Software Portal: An Integrated Platform for Collaborative Development},
+ booktitle = {Proceedings of the 13th International Symposium on Open Collaboration},
+ series = {OpenSym '17},
+ year = {2017},
+ isbn = {978-1-4503-5187-4},
+ location = {Galway, Ireland},
+ pages = {16:1--16:10},
+ articleno = {16},
+ numpages = {10},
+ url = {http://doi.acm.org/10.1145/3125433.3125471},
+ doi = {10.1145/3125433.3125471},
+ acmid = {3125471},
+ publisher = {ACM},
+ address = {New York, NY, USA},
+ keywords = {Free Software, Management Team, Software Integration}
+}
+
+@article{nerur2015challenges,
+ author = {Nerur, Sridhar and Mahapatra, RadhaKanta and Mangalaraj, George},
+ title = {Challenges of Migrating to Agile Methodologies},
+ journal = {Commun. ACM},
+ issue_date = {May 2005},
+ volume = {48},
+ number = {5},
+ month = may,
+ year = {2005},
+ issn = {0001-0782},
+ pages = {72--78},
+ numpages = {7},
+ url = {http://doi.acm.org/10.1145/1060710.1060712},
+ doi = {10.1145/1060710.1060712},
+ acmid = {1060712},
+ publisher = {ACM},
+ address = {New York, NY, USA},
+} 
+
+@inproceedings{strode2009impact,
+author = {Strode, Diane and Huff, Sid and Tretiakov, Alexei},
+year = {2009},
+month = {01},
+pages = {1-9},
+title = {The Impact of Organizational Culture on Agile Method Use.},
+booktitle = {Proceedings of the 42nd Hawaii International Conference on System Sciences}
+}
+
+@article{cho2011gap,
+author = {Chookittikul, Wajee and Kourik, Janet and E. Maher, Peter},
+year = {2011},
+month = {04},
+pages = {239-244},
+title = {Reducing the Gap between Academia and Industry: The Case for Agile Methods in Thailand},
+booktitle = {Proceedings of the 2011 Eighth International Conference on Information Technology: New Generations}
+}
+
 \section{Related work}
  
-There are similar previous works that we will review here. Agile methods application on the Brazilian public sector are approached by \cite{melo2010adoccao,de2016using}, but both are experiences limited to pilot projects. Not production-ready one that will provide more accurate data with the real world. On \cite{alleman2003making} the authors describe a production deployment for the US government, but it focus on describing the methodology applied to address long term planning and value estimation. And again on \cite{anderson2005stretching} we see a production software development case and the adaptation proposal that we will follow in this article, but focused on a specific methodology, the CMMI.
+Since the publication of the Agile Manisfeto in 2001, several researches have
+been evaluated the impacts and challenges in adopting agile
+methodologies in traditional culture organizations. Nerur et al. \cite{nerur2015challenges}
+identify the key issues that involve migrating from traditional to agile by
+comparing main practices of the two methodologies. In their work, the
+authors point out managerial, organizational, people, process and technological
+issues to be rethought and reconfigured in an organization for a
+successful migration. Strode et al. \cite{strode2009impact} investigate the correlation between
+adoption of agile methodologies and organizational culture. They evaluate the
+perception of organizational culture and the use of agile practices in nine
+software development projects and identify organizational culture factors
+that are correlated to the implementation of agile methods.
  
-This article differentiates itself from others by describing a production level software development to the public sector, but unconstrained to any specific aspect of the agile methods or an specific project management methodology on the government side. The focus on this article will be the whole experience of adapting agile methods to the public sector.
+
+The use of agile methods has also been investigated and explored in
+interactions between industry and academia. Chookittikul et al. \cite{cho2011gap} evaluate the
+increasing use of these methods by software development organizations in
+Thailand. To encourage the software industry growth in the region, the authors
+suggest universities create a curricula which develops in their undergraduate
+students practical skills required by industry (mainly agile practices).
+This can be achieved through some activities, such as, internships, agile
+development classes, real-world research projects, and collaboration between
+faculty and industry professionals. Sandberg et al. \cite{sandberg2017iacollaboration} report the implementation
+of SCRUM in a collaborative research consortium between industry and academia
+(involving ten industry partners and five universities in Sweden). They present
+which adaptations were made over 6 years to promote a effective use of agile
+practices, and also overcome differences of goals and pace.
+
+
+The challenges in agile methods implementation present new variables when
+involving government. Agile methods application on the Brazilian public sector
+are approached by Melo et al. \cite{melo2010adoccao} and De Sousa et al.
+\cite{de2016using}, but both are experiences limited to pilot projects. Not
+production-ready one that will provide more accurate data with the real world.
+Alleman et al. \cite{alleman2003making} describe a production deployment for
+the US government, but it focus on describing the methodology applied to
+address long term planning and value estimation.
+
+
+This paper differentiates itself from others by describing a production level
+software development collaboration between public sector and academia, but
+unconstrained to any specific aspect of the agile methods or an specific
+project management methodology on the government side. The focus on this
+paper is the whole experience of conciling the agile culture of academia
+with the traditional culture of the public sector, adapting the development
+practices and project management of those involved without transforming their
+internal processes.
+%Melhorar o que o diferencia dos demais
  
 % TODO: if needed, we can add this paper as related work
 %% Staying Agile in Government Software Projects - reports how the agile culture and practices (XP and Scrum) were introduced in a development team working on a government project. Describes practices added, adapted and abandoned. They had a experienced small team that did not know agile. TODO: Not sure if any process had to be added/adapted/abandoned at the government side.
+
+%Talvez seria relevante citar Extending Patterns for Fearless Change: sobre como introduzir novas ideias em uma organização tradicional (em particular, como introduzir métodos ágeis) 
+%O Mestrado do Alexandre Freire sobre como ensinar métodos ágeis que tem toda um capítulo sobre governo: https://www.ime.usp.br/~ale/dissertacao_ale_para_web.pdf
-\section{Problem Context}
-\label{sec:problem_context}
+\section{The Case Study}
+\label{sec:case_study}
  
 % What is the Brazilian government structure?
 % How are IT projects managed?
 % What were the conflicts between government and development team?
+In this section, we present the SPB platform (its goals and its users) and describe the three-years-long project for the evolution of the platform (its development and management process and its organizational structure: team, coordination, roles and interactions). We will also describe the governmental organizational structure and how they managed the project (staff, roles, documentation / reports required) and, finally, we will present possible points of conflict and their possible impacts on the project.
-\section{Methods}
-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:
+\section{Research Design}
+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?}
 \ No newline at end of file
+
+\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.
 \ No newline at end of file
 \section{Results}
+In this section, we present the results obtained through interviews and questionnaries with project participants, analysis of the communication and project management tools, and analysis of the code developed during the project for the softwares that integrate the platform.
 \begin{acks}
-  The authors would like to thank Dr. Yuhua Li for providing the
-  matlab code of  the \textit{BEPS} method.
-
-  The authors would also like to thank the anonymous referees for
-  their valuable comments and helpful suggestions. The work is
-  supported by the \grantsponsor{GS501100001809}{National Natural
-    Science Foundation of
-    China}{http://dx.doi.org/10.13039/501100001809} under Grant
-  No.:~\grantnum{GS501100001809}{61273304}
-  and~\grantnum[http://www.nnsf.cn/youngscientsts]{GS501100001809}{Young
-    Scientsts' Support Program}.
  
 \end{acks}
@@ -35,13 +35,11 @@
 \title{Conciliating distinct processes of management and software development}
 %\titlenote{Produces the permission block, and
 %  copyright information}
-\subtitle{A three-year empirical learning from the evolution of a government platform}
+\subtitle{A three-year empirical study from the evolution of a government platform}
 %\subtitlenote{The full version of the author's guide is available as
 %  \texttt{acmart.pdf} document}
  
-\author{Melissa Wen, Rodrigo Siqueira,
-        \\ Diego Camarinha, Arthur del Esposte,
-        \\Rafael Manzo, Lucas Kanashiro}
+\author{.}
 \affiliation{%
   \institution{FLOSS Competence Center \\ University of S\~ao Paulo}
   \streetaddress{Rua do Matão, 1010, Cidade Universitária}
@@ -50,9 +48,9 @@
   \country{Brazil}
   \postcode{05508-090}
 }
-\email{{wen,siqueira,esposte,lkd,diegoamc,manzo}@ime.usp.br}
+\email{@ime.usp.br}
  
-\author{Paulo Meirelles}
+\author{.}
 \affiliation{%
   \institution{Faculty Gama (FGA) \\ University of Bras\'ilia}
   \streetaddress{St. Leste Projeção A - Gama Leste}
@@ -61,10 +59,10 @@
   \country{Brazil}
   \postcode{72444-240}
 }
-\email{paulormm@unb.br}
+\email{@unb.br}
  
 % The default list of authors is too long for headers}
-\renewcommand{\shortauthors}{M. Wen et al.}
+\renewcommand{\shortauthors}{}
  
  
 \input{content/00-abstract}
@@ -75,7 +73,6 @@
 \input{content/01-introduction}
 \input{content/02-related_work}
 \input{content/03-context}
-\input{content/04-materials}
 \input{content/05-methods}
 \input{content/06-results}
 \input{content/07-discussion}
...	...	@@ -75,3 +75,77 @@
75	75	organization={IEEE}
76	76	}
77	77
	78	+@inproceedings{sandberg2017iacollaboration,
	79	+ author = {Sandberg, Anna B\"{o}rjesson and Crnkovic, Ivica},
	80	+ title = {Meeting Industry: Academia Research Collaboration Challenges with Agile Methodologies},
	81	+ booktitle = {Proceedings of the 39th International Conference on Software Engineering: Software Engineering in Practice Track},
	82	+ series = {ICSE-SEIP '17},
	83	+ year = {2017},
	84	+ isbn = {978-1-5386-2717-4},
	85	+ location = {Buenos Aires, Argentina},
	86	+ pages = {73--82},
	87	+ numpages = {10},
	88	+ url = {https://doi.org/10.1109/ICSE-SEIP.2017.20},
	89	+ doi = {10.1109/ICSE-SEIP.2017.20},
	90	+ acmid = {3103122},
	91	+ publisher = {IEEE Press},
	92	+ address = {Piscataway, NJ, USA},
	93	+ keywords = {agile methodologies, case study, collaboration, industry-academia research}
	94	+}
	95	+
	96	+@inproceedings{meirelles2017spb,
	97	+ author = {Meirelles, Paulo and Wen, Melissa and Terceiro, Antonio and Siqueira, Rodrigo and Kanashiro, Lucas and Neri, Hilmer},
	98	+ title = {Brazilian Public Software Portal: An Integrated Platform for Collaborative Development},
	99	+ booktitle = {Proceedings of the 13th International Symposium on Open Collaboration},
	100	+ series = {OpenSym '17},
	101	+ year = {2017},
	102	+ isbn = {978-1-4503-5187-4},
	103	+ location = {Galway, Ireland},
	104	+ pages = {16:1--16:10},
	105	+ articleno = {16},
	106	+ numpages = {10},
	107	+ url = {http://doi.acm.org/10.1145/3125433.3125471},
	108	+ doi = {10.1145/3125433.3125471},
	109	+ acmid = {3125471},
	110	+ publisher = {ACM},
	111	+ address = {New York, NY, USA},
	112	+ keywords = {Free Software, Management Team, Software Integration}
	113	+}
	114	+
	115	+@article{nerur2015challenges,
	116	+ author = {Nerur, Sridhar and Mahapatra, RadhaKanta and Mangalaraj, George},
	117	+ title = {Challenges of Migrating to Agile Methodologies},
	118	+ journal = {Commun. ACM},
	119	+ issue_date = {May 2005},
	120	+ volume = {48},
	121	+ number = {5},
	122	+ month = may,
	123	+ year = {2005},
	124	+ issn = {0001-0782},
	125	+ pages = {72--78},
	126	+ numpages = {7},
	127	+ url = {http://doi.acm.org/10.1145/1060710.1060712},
	128	+ doi = {10.1145/1060710.1060712},
	129	+ acmid = {1060712},
	130	+ publisher = {ACM},
	131	+ address = {New York, NY, USA},
	132	+}
	133	+
	134	+@inproceedings{strode2009impact,
	135	+author = {Strode, Diane and Huff, Sid and Tretiakov, Alexei},
	136	+year = {2009},
	137	+month = {01},
	138	+pages = {1-9},
	139	+title = {The Impact of Organizational Culture on Agile Method Use.},
	140	+booktitle = {Proceedings of the 42nd Hawaii International Conference on System Sciences}
	141	+}
	142	+
	143	+@article{cho2011gap,
	144	+author = {Chookittikul, Wajee and Kourik, Janet and E. Maher, Peter},
	145	+year = {2011},
	146	+month = {04},
	147	+pages = {239-244},
	148	+title = {Reducing the Gap between Academia and Industry: The Case for Agile Methods in Thailand},
	149	+booktitle = {Proceedings of the 2011 Eighth International Conference on Information Technology: New Generations}
	150	+}
	151	+
...	...
1	1	\section{Related work}
2	2
3		-There are similar previous works that we will review here. Agile methods application on the Brazilian public sector are approached by \cite{melo2010adoccao,de2016using}, but both are experiences limited to pilot projects. Not production-ready one that will provide more accurate data with the real world. On \cite{alleman2003making} the authors describe a production deployment for the US government, but it focus on describing the methodology applied to address long term planning and value estimation. And again on \cite{anderson2005stretching} we see a production software development case and the adaptation proposal that we will follow in this article, but focused on a specific methodology, the CMMI.
	3	+Since the publication of the Agile Manisfeto in 2001, several researches have
	4	+been evaluated the impacts and challenges in adopting agile
	5	+methodologies in traditional culture organizations. Nerur et al. \cite{nerur2015challenges}
	6	+identify the key issues that involve migrating from traditional to agile by
	7	+comparing main practices of the two methodologies. In their work, the
	8	+authors point out managerial, organizational, people, process and technological
	9	+issues to be rethought and reconfigured in an organization for a
	10	+successful migration. Strode et al. \cite{strode2009impact} investigate the correlation between
	11	+adoption of agile methodologies and organizational culture. They evaluate the
	12	+perception of organizational culture and the use of agile practices in nine
	13	+software development projects and identify organizational culture factors
	14	+that are correlated to the implementation of agile methods.
4	15
5		-This article differentiates itself from others by describing a production level software development to the public sector, but unconstrained to any specific aspect of the agile methods or an specific project management methodology on the government side. The focus on this article will be the whole experience of adapting agile methods to the public sector.
	16	+
	17	+The use of agile methods has also been investigated and explored in
	18	+interactions between industry and academia. Chookittikul et al. \cite{cho2011gap} evaluate the
	19	+increasing use of these methods by software development organizations in
	20	+Thailand. To encourage the software industry growth in the region, the authors
	21	+suggest universities create a curricula which develops in their undergraduate
	22	+students practical skills required by industry (mainly agile practices).
	23	+This can be achieved through some activities, such as, internships, agile
	24	+development classes, real-world research projects, and collaboration between
	25	+faculty and industry professionals. Sandberg et al. \cite{sandberg2017iacollaboration} report the implementation
	26	+of SCRUM in a collaborative research consortium between industry and academia
	27	+(involving ten industry partners and five universities in Sweden). They present
	28	+which adaptations were made over 6 years to promote a effective use of agile
	29	+practices, and also overcome differences of goals and pace.
	30	+
	31	+
	32	+The challenges in agile methods implementation present new variables when
	33	+involving government. Agile methods application on the Brazilian public sector
	34	+are approached by Melo et al. \cite{melo2010adoccao} and De Sousa et al.
	35	+\cite{de2016using}, but both are experiences limited to pilot projects. Not
	36	+production-ready one that will provide more accurate data with the real world.
	37	+Alleman et al. \cite{alleman2003making} describe a production deployment for
	38	+the US government, but it focus on describing the methodology applied to
	39	+address long term planning and value estimation.
	40	+
	41	+
	42	+This paper differentiates itself from others by describing a production level
	43	+software development collaboration between public sector and academia, but
	44	+unconstrained to any specific aspect of the agile methods or an specific
	45	+project management methodology on the government side. The focus on this
	46	+paper is the whole experience of conciling the agile culture of academia
	47	+with the traditional culture of the public sector, adapting the development
	48	+practices and project management of those involved without transforming their
	49	+internal processes.
	50	+%Melhorar o que o diferencia dos demais
6	51
7	52	% TODO: if needed, we can add this paper as related work
8	53	%% Staying Agile in Government Software Projects - reports how the agile culture and practices (XP and Scrum) were introduced in a development team working on a government project. Describes practices added, adapted and abandoned. They had a experienced small team that did not know agile. TODO: Not sure if any process had to be added/adapted/abandoned at the government side.
	54	+
	55	+%Talvez seria relevante citar Extending Patterns for Fearless Change: sobre como introduzir novas ideias em uma organização tradicional (em particular, como introduzir métodos ágeis)
	56	+%O Mestrado do Alexandre Freire sobre como ensinar métodos ágeis que tem toda um capítulo sobre governo: https://www.ime.usp.br/~ale/dissertacao_ale_para_web.pdf
...	...
1		-\section{Problem Context}
2		-\label{sec:problem_context}
	1	+\section{The Case Study}
	2	+\label{sec:case_study}
3	3
4	4	% What is the Brazilian government structure?
5	5	% How are IT projects managed?
6	6	% What were the conflicts between government and development team?
	7	+In this section, we present the SPB platform (its goals and its users) and describe the three-years-long project for the evolution of the platform (its development and management process and its organizational structure: team, coordination, roles and interactions). We will also describe the governmental organizational structure and how they managed the project (staff, roles, documentation / reports required) and, finally, we will present possible points of conflict and their possible impacts on the project.
...	...
1		-\section{Methods}
2		-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:
	1	+\section{Research Design}
	2	+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}.
	3	+
	4	+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:
3	5	%
4	6
	7	+
5	8	\textbf{Q1.} \textit{Can teams with distinct software development processes be well combined in the same project?}
6	9	%
7	10
8		-\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?}
9	11	\ No newline at end of file
	12	+
	13	+\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?}
	14	+
	15	+
	16	+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:
	17	+
	18	+\begin{enumerate}
	19	+ \item \textit{sending a questionnaire to all students}
	20	+ \item \textit{sending an open questionnaire to IT professionals}
	21	+ \item \textit{interviewing government representatives involved in the project.}
	22	+ \end{enumerate}
	23	+
	24	+(Describe questionnaires and interviews)
	25	+
	26	+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.
	27	+
	28	+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.
10	29	\ No newline at end of file
...	...
1	1	\section{Results}
	2	+In this section, we present the results obtained through interviews and questionnaries with project participants, analysis of the communication and project management tools, and analysis of the code developed during the project for the softwares that integrate the platform.
...	...
1	1	\begin{acks}
2		- The authors would like to thank Dr. Yuhua Li for providing the
3		- matlab code of the \textit{BEPS} method.
4		-
5		- The authors would also like to thank the anonymous referees for
6		- their valuable comments and helpful suggestions. The work is
7		- supported by the \grantsponsor{GS501100001809}{National Natural
8		- Science Foundation of
9		- China}{http://dx.doi.org/10.13039/501100001809} under Grant
10		- No.:~\grantnum{GS501100001809}{61273304}
11		- and~\grantnum[http://www.nnsf.cn/youngscientsts]{GS501100001809}{Young
12		- Scientsts' Support Program}.
13	2
14	3	\end{acks}
...	...
...	...	@@ -35,13 +35,11 @@
35	35	\title{Conciliating distinct processes of management and software development}
36	36	%\titlenote{Produces the permission block, and
37	37	% copyright information}
38		-\subtitle{A three-year empirical learning from the evolution of a government platform}
	38	+\subtitle{A three-year empirical study from the evolution of a government platform}
39	39	%\subtitlenote{The full version of the author's guide is available as
40	40	% \texttt{acmart.pdf} document}
41	41
42		-\author{Melissa Wen, Rodrigo Siqueira,
43		- \\ Diego Camarinha, Arthur del Esposte,
44		- \\Rafael Manzo, Lucas Kanashiro}
	42	+\author{.}
45	43	\affiliation{%
46	44	\institution{FLOSS Competence Center \\ University of S\~ao Paulo}
47	45	\streetaddress{Rua do Matão, 1010, Cidade Universitária}
...	...	@@ -50,9 +48,9 @@
50	48	\country{Brazil}
51	49	\postcode{05508-090}
52	50	}
53		-\email{{wen,siqueira,esposte,lkd,diegoamc,manzo}@ime.usp.br}
	51	+\email{@ime.usp.br}
54	52
55		-\author{Paulo Meirelles}
	53	+\author{.}
56	54	\affiliation{%
57	55	\institution{Faculty Gama (FGA) \\ University of Bras\'ilia}
58	56	\streetaddress{St. Leste Projeção A - Gama Leste}
...	...	@@ -61,10 +59,10 @@
61	59	\country{Brazil}
62	60	\postcode{72444-240}
63	61	}
64		-\email{paulormm@unb.br}
	62	+\email{@unb.br}
65	63
66	64	% The default list of authors is too long for headers}
67		-\renewcommand{\shortauthors}{M. Wen et al.}
	65	+\renewcommand{\shortauthors}{}
68	66
69	67
70	68	\input{content/00-abstract}
...	...	@@ -75,7 +73,6 @@
75	73	\input{content/01-introduction}
76	74	\input{content/02-related_work}
77	75	\input{content/03-context}
78		-\input{content/04-materials}
79	76	\input{content/05-methods}
80	77	\input{content/06-results}
81	78	\input{content/07-discussion}
...	...