Download as
Browse Code »

Commit c89935f34be347a1afa2611ed7948572aa0986cb

Authored by Melissa Wen
1 parent c51344f5
Exists in master and in 3 other branches oss_2018, oss_2018_siqueira, rework_case_study

[oss-2018] refining introduction

Showing 4 changed files with 137 additions and 158 deletions   Show diff stats
icse2018/content/01-introduction.tex
  Diff comments   View file @c89935f
... ... @@ -3,49 +3,44 @@
3 3 %Falar sobre unir tradicional (guiado por tarefas e atividades) e agil (guiado por funcionalidades) - nerur et al
4 4 %Falar sobre mudanças estrutura organizacional organica (agil) e burocratica (tradicional)
5 5  
6   -E-government projects are different from the others due to their complexity in
7   -terms of organizational size, proportional resistance to changes, innovation,
8   -impacts to end users and policies.
9   -%TODO: precisamos de uma referência de e-gov ^
10   -The partnership between government and
11   -academia could be seen as a means of transferring technological knowledge for
12   -the creation of innovative e-government projects. This type of collaboration has
13   -challenges not only in the organization of the project and the alignment of
14   -objectives and rhythms, but also to overcome the high probability of failure of
15   -e-government projects.
16   -%
17   -Despite the various solutions proposed to prevent project
18   -failure, none of them actually seems to reduce this rate, which generates not
19   -only a waste of money but also a lack of services offered to society.
20   -%TODO: Isto aqui ^ é em forte. Será que conseguimos uma referência?
21   -Among the
22   -reasons for this failure, poor project management is one of the main.
  6 +E-government projects differ from others due to their complexity and
  7 +extension\cite{anthopoulos2016egovernment}. They are extensive in terms of
  8 +organizational size, time, scope, target audience and corresponding resistance
  9 +to change. They are also complex by combining construction, innovation and ICT
  10 +in their context, in addition to politics and social impact. In order to
  11 +create novelty for e-government projects and meet the needs of society, research
  12 +collaboration between government and academia can be considered as a way to
  13 +transfer technological knowledge. However, such collaboration also has
  14 +challenges, not only in relation to project organization and alignment of goals
  15 +and pace \cite{sandberg2017iacollaboration}, but also to overcome the failure
  16 +trend of e-government projects \cite{goldfinch2007pessimism}.
23 17  
24   -Several development processes were introduced with the intention to increase
25   -the chances of success in software projects. Traditional methods have been used
26   -for a long time as a way to discipline the software development process. These
27   -methodologies can be characterized by the predictive approach, focus on
28   -documentation, processes oriented, and heavy based on
29   -tools\cite{comparisonAgileTraditional}. Agile methods, on the other hand,
30   -embraces the adaptative approach. It is characterized by the people-oriented
31   -approach \cite{agileSoftwareDevelopment}, the collaboration with clients
32   -\cite{theNewMethodology}, small selforganized teams \cite{peopleFactor}, and
33   -the flexibility regarding planning \cite{agileSoftwareDevelopmentEco}. In a
34   -nutshell, all methodologies intend to increase the chance of the project
35   -success. While industry and academia are aligned on the use of agile
36   -methodologies for software development, the traditional approach is still
37   -preferred by the government.
38   -%TODO: Vamos generalizar apenas afirmar no contexto Brasileiro? Brazilian government ^
  18 +One of the most common reasons for project failure is inefficient project
  19 +management \cite{anthopoulos2016egovernment}. Several development processes were
  20 +introduced with the intention to increase the chances of software projects
  21 +success. The traditional approach has long been used to discipline the software
  22 +development process. It is a predictive approach, focus on documentation,
  23 +processes oriented, and heavy based on tools \cite{awad2005comparisonAgileTrad}.
  24 +On the other hand, agile methodologies embrace the adaptive software development.
  25 +It is characterized by people-oriented approach
  26 +\cite{highsmith2001agileSoftwareDevelopment}, the collaboration with clients
  27 +\cite{fowler2001newMethod}, small self-organized teams
  28 +\cite{cockburn2001peopleFactor}, and the flexibility regarding planning
  29 +\cite{highsmith2002agileEco}. In a nutshell, both methodologies intend to
  30 +increase the chance of the project success.
39 31  
40   -When government and academia decide to come together for the development of an
41   -e-government solution, management processes of each institution needs to be
42   -aligned. Changing the software development process represents a complex
43   -organizational change that impact several aspects such as structure, culture,
44   -and management practices. However, neither culture nor values can be easily
45   -change, as well as, the effort for this kind of movement does not seem feasible
46   -for development projects with tight deadlines and budgets.
  32 +In Brazil, while industry and academia are aligned on the use of agile
  33 +methodologies for software development, the traditional approach is still
  34 +preferred by the government. When government and academia decide to come
  35 +together for the development of an e-government solution, management processes
  36 +of each institution needs to be aligned. Changing the software development
  37 +process represents a complex organizational change that impact several aspects
  38 +such as structure, culture, and management practices\cite{nerur2015challenges}.
  39 +However, neither culture nor values can be easily change and the effort for this
  40 +kind of movement does not seem feasible for development projects with tight
  41 +deadlines and budgets.
47 42  
48   -This paper present practical ways to harmonize traditional and agile
  43 +This paper present practical ways to harmonize the traditional and agile
49 44 approach in the management of a partnership project between government and
50 45 academia. For this, we interviewed members involved in the project with distinct
51 46 roles: requirement analysts and stakeholders of the Brazilian Ministry of
... ... @@ -54,13 +49,13 @@ senior developers. We also analyze data collected from the management and
54 49 communication tools. We these results, we evidence best practices adopted on a
55 50 30-months project to create an unprecedented platform for the Brazilian
56 51 government. We also validate lessons learned reported in our previous
57   -work\cite{meirelles2017spb}.
  52 +work \cite{meirelles2017spb}.
58 53  
59 54 % TODO: Verificar as seções
60   -Section \ref{sec:relatedwork} discuss the related work on blablabla. Section
61   -\ref{sec:casestudy} presents blablabla. Section \ref{sec:researchdesign}
62   -describes our research questions and methodology. Section \ref{sec:discussion}
  55 +Section \ref{sec:relatedwork} describes related work. Section
  56 +\ref{sec:casestudy} gives a brief description of the case study. Section \ref{sec:researchdesign}
  57 +describes our research questions and methodology. Section \ref{sec:discussion}
63 58 presents findings derived from our quantitative and qualitative analyses.
64   -Section \ref{sec:results} we describe the results. Finally, we present the
  59 +Section \ref{sec:results} we describe the results. Finally, we present the
65 60 limitations, related work and conclusions.
66 61  
... ...
icse2018/content/03-relatedwork.tex
  Diff comments   View file @c89935f
... ... @@ -34,7 +34,7 @@ practices, and also overcome differences of goals and pace.
34 34 The challenges in agile methods implementation present new variables when
35 35 involving government. Agile methods application on the Brazilian public sector
36 36 are approached by Melo et al. and De Sousa et al.
37   -\cite{melo2010adoccao,de2016using}, but both are experiences limited to pilot
  37 +\cite{melo2013agileBr,de2016using}, but both are experiences limited to pilot
38 38 projects. Not production-ready one that will provide more accurate data with
39 39 the real world. Alleman et al. describe a production deployment for the US
40 40 government, but it focus on describing the methodology applied to address long
... ... @@ -50,7 +50,6 @@ sides. The focus on this paper is the whole experience of conciling the agile
50 50 culture of academia with the traditional culture of the public sector, adapting
51 51 the development practices and project management of those involved without
52 52 transforming their internal processes.
53   -%Melhorar o que o diferencia dos demais
54 53  
55 54 % TODO: if needed, we can add this paper as related work
56 55 %% 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.
... ...
icse2018/content/04-case.tex
  Diff comments   View file @c89935f
1 1 \section{The Case Study}
2 2 \label{sec:casestudy}
3 3  
  4 +%TODO Repensar a escrita
  5 +
4 6  
5 7 The Brazilian Public Software portal is an e-government project for sharing
6 8 public software projects, specific type of systems that meets the needs of
... ...
icse2018/spb-oss-2018.bib
  Diff comments   View file @c89935f
1   -@article{agileSoftwareDevelopment,
  1 +@article{anthopoulos2016egovernment,
  2 + title={Why e-government projects fail? An analysis of the Healthcare. gov website},
  3 + author={Anthopoulos, Leonidas and Reddick, Christopher G and Giannakidou, Irene and Mavridis, Nikolaos},
  4 + journal={Government Information Quarterly},
  5 + volume={33},
  6 + number={1},
  7 + pages={161--173},
  8 + year={2016},
  9 + publisher={Elsevier}
  10 +}
  11 +
  12 +@inproceedings{sandberg2017iacollaboration,
  13 + author = {Sandberg, Anna B\"{o}rjesson and Crnkovic, Ivica},
  14 + title = {Meeting Industry: Academia Research Collaboration Challenges with Agile Methodologies},
  15 + booktitle = {Proceedings of the 39th International Conference on Software Engineering: Software Engineering in Practice Track},
  16 + series = {ICSE-SEIP '17},
  17 + year = {2017},
  18 + isbn = {978-1-5386-2717-4},
  19 + location = {Buenos Aires, Argentina},
  20 + pages = {73--82},
  21 + numpages = {10},
  22 + url = {https://doi.org/10.1109/ICSE-SEIP.2017.20},
  23 + doi = {10.1109/ICSE-SEIP.2017.20},
  24 + acmid = {3103122},
  25 + publisher = {IEEE Press},
  26 + address = {Piscataway, NJ, USA},
  27 + keywords = {agile methodologies, case study, collaboration, industry-academia research}
  28 +}
  29 +
  30 +
  31 +@article{goldfinch2007pessimism,
  32 + ISSN={00333352, 15406210},
  33 + URL={http://www.jstor.org/stable/4624644},
  34 + author={Shaun Goldfinch},
  35 + journal={Public Administration Review},
  36 + number={5},
  37 + pages={917-929},
  38 + publisher={[American Society for Public Administration, Wiley]},
  39 + title={Pessimism, Computer Failure, and Information Systems Development in the Public Sector},
  40 + volume={67},
  41 + year={2007}
  42 +}
  43 +
  44 +@article{highsmith2001agileSoftwareDevelopment,
2 45 title={Agile software development: The business of innovation},
3 46 author={Highsmith, Jim and Cockburn, Alistair},
4 47 journal={Computer},
... ... @@ -9,7 +52,7 @@
9 52 publisher={IEEE}
10 53 }
11 54  
12   -@inproceedings{onTheProductivityOfAgile,
  55 +@inproceedings{maurer2002onTheProductivityOfAgile,
13 56 title={On the productivity of agile software practices: An industrial case study},
14 57 author={Maurer, Frank and Martel, Sebastien},
15 58 booktitle={Proceedings of the International Workshop on Global Software Development},
... ... @@ -23,7 +66,7 @@
23 66 publisher={NATO Scientific Affairs Division}
24 67 }
25 68  
26   -@inproceedings{anAnalysisOfTrends,
  69 +@inproceedings{nguyen2011anAnalysisOfTrends,
27 70 title={An analysis of trends in productivity and cost drivers over years},
28 71 author={Nguyen, Vu and Huang, LiGuo and Boehm, Barry},
29 72 booktitle={Proceedings of the 7th International Conference on Predictive Models in Software Engineering},
... ... @@ -32,14 +75,14 @@
32 75 organization={ACM}
33 76 }
34 77  
35   -@article{comparisonAgileTraditional,
  78 +@article{awad2005comparisonAgileTrad,
36 79 title={A comparison between agile and traditional software development methodologies},
37 80 author={Awad, MA},
38 81 journal={University of Western Australia},
39 82 year={2005}
40 83 }
41 84  
42   -@article{theNewMethodology,
  85 +@article{fowler2001newMethod,
43 86 title={The new methodology},
44 87 author={Fowler, Martin},
45 88 journal={Wuhan University Journal of Natural Sciences},
... ... @@ -50,7 +93,7 @@
50 93 publisher={Springer}
51 94 }
52 95  
53   -@article{peopleFactor,
  96 +@article{cockburn2001peopleFactor,
54 97 title={Agile software development, the people factor},
55 98 author={Cockburn, Alistair and Highsmith, Jim},
56 99 journal={Computer},
... ... @@ -61,7 +104,7 @@
61 104 publisher={IEEE}
62 105 }
63 106  
64   -@book{agileSoftwareDevelopmentEco,
  107 +@book{highsmith2002agileEco,
65 108 title={Agile software development ecosystems},
66 109 author={Highsmith, James A},
67 110 volume={13},
... ... @@ -69,15 +112,42 @@
69 112 publisher={Addison-Wesley Professional}
70 113 }
71 114  
72   -@article{challengesOfMigrating,
73   - title={Challenges of migrating to agile methodologies},
74   - author={Nerur, Sridhar and Mahapatra, RadhaKanta and Mangalaraj, George},
75   - journal={Communications of the ACM},
76   - volume={48},
77   - number={5},
78   - pages={72--78},
79   - year={2005},
80   - publisher={ACM}
  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{meirelles2017spb,
  135 + author = {Meirelles, Paulo and Wen, Melissa and Terceiro, Antonio and Siqueira, Rodrigo and Kanashiro, Lucas and Neri, Hilmer},
  136 + title = {Brazilian Public Software Portal: An Integrated Platform for Collaborative Development},
  137 + booktitle = {Proceedings of the 13th International Symposium on Open Collaboration},
  138 + series = {OpenSym '17},
  139 + year = {2017},
  140 + isbn = {978-1-4503-5187-4},
  141 + location = {Galway, Ireland},
  142 + pages = {16:1--16:10},
  143 + articleno = {16},
  144 + numpages = {10},
  145 + url = {http://doi.acm.org/10.1145/3125433.3125471},
  146 + doi = {10.1145/3125433.3125471},
  147 + acmid = {3125471},
  148 + publisher = {ACM},
  149 + address = {New York, NY, USA},
  150 + keywords = {Free Software, Management Team, Software Integration}
81 151 }
82 152  
83 153 @inproceedings{impactOfOrganizationalCulture,
... ... @@ -89,40 +159,6 @@
89 159 organization={IEEE}
90 160 }
91 161  
92   -@incollection{layeredApproach,
93   - title={The structure of the “THE” multiprogramming system},
94   - author={Dijkstra, Edsger W},
95   - booktitle={The origin of concurrent programming},
96   - pages={139--152},
97   - year={1968},
98   - publisher={Springer}
99   -}
100   -
101   -@article{anthopoulos2016government,
102   - title={Why e-government projects fail? An analysis of the Healthcare. gov website},
103   - author={Anthopoulos, Leonidas and Reddick, Christopher G and Giannakidou, Irene and Mavridis, Nikolaos},
104   - journal={Government Information Quarterly},
105   - volume={33},
106   - number={1},
107   - pages={161--173},
108   - year={2016},
109   - publisher={Elsevier}
110   -}
111   -
112   -@article{goldfinch2007pessimism,
113   - ISSN={00333352, 15406210},
114   - URL={http://www.jstor.org/stable/4624644},
115   - abstract={The majority of information systems developments are unsuccessful. The larger the development, the more likely it will be unsuccessful. Despite the persistence of this problem for decades and the expenditure of vast sums of money, computer failure has received surprisingly little attention in the public administration literature. This article outlines the problems of enthusiasm and the problems of control, as well as the overwhelming complexity, that make the failure of large developments almost inevitable. Rather than the positive view found in much of the public administration literature, the author suggests a pessimism when it comes to information systems development. Aims for information technology should be modest ones, and in many cases, the risks, uncertainties, and probability of failure mean that new investments in technology are not justified. The author argues for a public official as a recalcitrant, suspicious, and skeptical adopter of IT.},
116   - author={Shaun Goldfinch},
117   - journal={Public Administration Review},
118   - number={5},
119   - pages={917-929},
120   - publisher={[American Society for Public Administration, Wiley]},
121   - title={Pessimism, Computer Failure, and Information Systems Development in the Public Sector},
122   - volume={67},
123   - year={2007}
124   -}
125   -
126 162 @article{dybaa2008empirical,
127 163 title={Empirical studies of agile software development: A systematic review},
128 164 author={Dyb{\aa}, Tore and Dings{\o}yr, Torgeir},
... ... @@ -143,11 +179,14 @@
143 179 organization={IEEE}
144 180 }
145 181  
146   -@inproceedings{melo2010adoccao,
147   - title={Ado{\c{c}}{\~a}o de m{\'e}todos {\'a}geis em uma Institui{\c{c}}{\~a}o P{\'u}blica de grande porte-um estudo de caso},
148   - author={Melo, Claudia de O and Ferreira, Gisele RM},
149   - booktitle={Workshop Brasileiro de M{\'e}todos {\'A}geis (Agile Brasil 2010). Centro de Eventos da PUCRS (CEPUC), Porto Alegre},
150   - year={2010}
  182 +@inproceedings{melo2013agileBr,
  183 + author = {Melo, Claudia and Santos, Viviane and Katayama, Eduardo and Corbucci, Hugo and Prikladnicki, Rafael and Goldman, Alfredo and Kon, Fabio},
  184 + year = {2013},
  185 + month = {11},
  186 + pages = {},
  187 + title = {The evolution of agile software development in Brazil},
  188 + volume = {19},
  189 + booktitle = {Journal of the Brazilian Computer Society}
151 190 }
152 191  
153 192 @inproceedings{alleman2003making,
... ... @@ -168,62 +207,6 @@
168 207 organization={IEEE}
169 208 }
170 209  
171   -@inproceedings{sandberg2017iacollaboration,
172   - author = {Sandberg, Anna B\"{o}rjesson and Crnkovic, Ivica},
173   - title = {Meeting Industry: Academia Research Collaboration Challenges with Agile Methodologies},
174   - booktitle = {Proceedings of the 39th International Conference on Software Engineering: Software Engineering in Practice Track},
175   - series = {ICSE-SEIP '17},
176   - year = {2017},
177   - isbn = {978-1-5386-2717-4},
178   - location = {Buenos Aires, Argentina},
179   - pages = {73--82},
180   - numpages = {10},
181   - url = {https://doi.org/10.1109/ICSE-SEIP.2017.20},
182   - doi = {10.1109/ICSE-SEIP.2017.20},
183   - acmid = {3103122},
184   - publisher = {IEEE Press},
185   - address = {Piscataway, NJ, USA},
186   - keywords = {agile methodologies, case study, collaboration, industry-academia research}
187   -}
188   -
189   -@inproceedings{meirelles2017spb,
190   - author = {Meirelles, Paulo and Wen, Melissa and Terceiro, Antonio and Siqueira, Rodrigo and Kanashiro, Lucas and Neri, Hilmer},
191   - title = {Brazilian Public Software Portal: An Integrated Platform for Collaborative Development},
192   - booktitle = {Proceedings of the 13th International Symposium on Open Collaboration},
193   - series = {OpenSym '17},
194   - year = {2017},
195   - isbn = {978-1-4503-5187-4},
196   - location = {Galway, Ireland},
197   - pages = {16:1--16:10},
198   - articleno = {16},
199   - numpages = {10},
200   - url = {http://doi.acm.org/10.1145/3125433.3125471},
201   - doi = {10.1145/3125433.3125471},
202   - acmid = {3125471},
203   - publisher = {ACM},
204   - address = {New York, NY, USA},
205   - keywords = {Free Software, Management Team, Software Integration}
206   -}
207   -
208   -@article{nerur2015challenges,
209   - author = {Nerur, Sridhar and Mahapatra, RadhaKanta and Mangalaraj, George},
210   - title = {Challenges of Migrating to Agile Methodologies},
211   - journal = {Commun. ACM},
212   - issue_date = {May 2005},
213   - volume = {48},
214   - number = {5},
215   - month = may,
216   - year = {2005},
217   - issn = {0001-0782},
218   - pages = {72--78},
219   - numpages = {7},
220   - url = {http://doi.acm.org/10.1145/1060710.1060712},
221   - doi = {10.1145/1060710.1060712},
222   - acmid = {1060712},
223   - publisher = {ACM},
224   - address = {New York, NY, USA}
225   -}
226   -
227 210 @article{cho2011gap,
228 211 author = {Chookittikul, Wajee and Kourik, Janet and E. Maher, Peter},
229 212 year = {2011},
... ...