Download as
Browse Code »

Commit da1e424b4b02195af1fa4077f6cb4e64d4f01af3

Authored by Paulo Meireles
1 parent 253a3ae3
Exists in master and in 3 other branches oss_2018, oss_2018_siqueira, rework_case_study

[oss2018] Introduction: minor corrections and adding comments

Showing 1 changed file with 34 additions and 26 deletions   Show diff stats
icse2018/content/01-introduction.tex
  Diff comments   View file @da1e424
... ... @@ -3,46 +3,53 @@
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   -Egovernment projects are different from the others due to their complexity in
  6 +E-government projects are different from the others due to their complexity in
7 7 terms of organizational size, proportional resistance to changes, innovation,
8   -impacts to end users and policies. The partnership between government and
  8 +impacts to end users and policies.
  9 +%TODO: precisamos de uma referência de e-gov ^
  10 +The partnership between government and
9 11 academia could be seen as a means of transferring technological knowledge for
10 12 the creation of innovative e-government projects. This type of collaboration has
11 13 challenges not only in the organization of the project and the alignment of
12 14 objectives and rhythms, but also to overcome the high probability of failure of
13   -e-government projects. Despite the various solutions proposed to prevent project
  15 +e-government projects.
  16 +%
  17 +Despite the various solutions proposed to prevent project
14 18 failure, none of them actually seems to reduce this rate, which generates not
15   -only a waste of money but also a lack of services offered to society. Among the
  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
16 22 reasons for this failure, poor project management is one of the main.
17 23  
18 24 Several development processes were introduced with the intention to increase
19   -the chances of success in software projects, the traditional and agile methods
20   -are the most popular. The traditional method has been used for a long time as a
21   -way to discipline the software development process. This methodology can be
22   -characterized by the predictive approach, focus on documentation, processes
23   -oriented, and heavy based on tools\cite{comparisonAgileTraditional}. The agile
24   -method, on the other hand, embraces the adaptative approach. It is characterized
25   -by the people-oriented approach \cite{agileSoftwareDevelopment}, the
26   -collaboration with clients \cite{theNewMethodology}, small selforganized teams
27   -\cite{peopleFactor}, and the flexibility regarding planning
28   -\cite{agileSoftwareDevelopmentEco}. In a nutshell, both methodologies intend to
29   -increase the chance of the project success. While industry and academia are
30   -aligned on the use of agile methodologies for software development, the
31   -traditional approach is still preferred by the government.
  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 ^
32 39  
33 40 When government and academia decide to come together for the development of an
34 41 e-government solution, management processes of each institution needs to be
35 42 aligned. Changing the software development process represents a complex
36 43 organizational change that impact several aspects such as structure, culture,
37 44 and management practices. However, neither culture nor values can be easily
38   -change and the effort for this kind of movement does not seem feasible for
39   -development projects with tight deadlines and budgets.
  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.
40 47  
41   -This paper present practical ways to harmonize the traditional and agile
  48 +This paper present practical ways to harmonize traditional and agile
42 49 approach in the management of a partnership project between government and
43 50 academia. For this, we interviewed members involved in the project with distinct
44 51 roles: requirement analysts and stakeholders of the Brazilian Ministry of
45   -Planning (MPOG), students from the University of Brasília and São Paulo and
  52 +Planning (MPOG), students from the University of Brasília and São Paulo, and
46 53 senior developers. We also analyze data collected from the management and
47 54 communication tools. We these results, we evidence best practices adopted on a
48 55 30-months project to create an unprecedented platform for the Brazilian
... ... @@ -50,9 +57,10 @@ government. We also validate lessons learned reported in our previous
50 57 work\cite{meirelles2017spb}.
51 58  
52 59 % TODO: Verificar as seções
53   -Section \ref{sec:relatedwork} discuss the related work on blablabla. Section \ref{sec:casestudy} presents blablabla. Section
54   -\ref{sec:researchdesign} describes our research questions and methodology.
55   -Section \ref{sec:discussion} presents findings derived from our quantitative
56   -and qualitative analyses. Section \ref{sec:results} we describe the results.
57   -Finally, we present the limitations, related work and conclusions.
  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}
  63 +presents findings derived from our quantitative and qualitative analyses.
  64 +Section \ref{sec:results} we describe the results. Finally, we present the
  65 +limitations, related work and conclusions.
58 66  
... ...