From 20b8d9844526f75ed9c5d88f750de77b6803e9ae Mon Sep 17 00:00:00 2001 From: rodrigosiqueira Date: Mon, 15 Jan 2018 22:01:00 -0200 Subject: [PATCH] Introdução e Related work revisada e atualizada --- oss2018/content/01-introduction.tex | 50 ++++++++++++++++++++++++++++---------------------- oss2018/content/02-relatedwork.tex | 100 ++++++++++++++++++++++++++++++++++++++++++++++++---------------------------------------------------- oss2018/spb-oss-2018.bib | 101 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++--------------------------------- 3 files changed, 144 insertions(+), 107 deletions(-) diff --git a/oss2018/content/01-introduction.tex b/oss2018/content/01-introduction.tex index 9f590ca..f90b5d4 100644 --- a/oss2018/content/01-introduction.tex +++ b/oss2018/content/01-introduction.tex @@ -3,32 +3,38 @@ E-government projects differ from others due to their complexity and extension \cite{anthopoulos2016egovernment}. They are complex because they combine construction, innovation, information \& communications technologies, politics, -and social impact. Their extension, on the other hand, is related to their scope, -target audience, organizational size, time, and the corresponding resistance to -change. Government-academia collaborative projects can be considered an -alternative to create novelty for e-government projects and to meet the needs of -society. This collaborative work has challenges, such as organizing the -collaboration project, aligning goals, synchronizing the pace of between +and social impact. Their extension, on the other hand, is related to their +scope, target audience, organizational size, time, and the corresponding +resistance to change. Government-academia collaborative projects may be treated +as an alternative to create novelty for e-government projects and to meet the +needs of society. This collaborative work has challenges, such as organizing +the collaboration project, aligning goals, synchronizing the pace of between government and academia \cite{anthopoulos2016egovernment}, and overcoming the failure trend of e-government projects \cite{goldfinch2007pessimism}. -Poor project management is one of the main reasons why e-government projects -fail \cite{anthopoulos2016egovernment}. When government and academia combine -efforts to develop an e-government solution, the differences in the project -management become an issue. Academia commonly work on cutting edge of -technology while government is still relying on traditional techniques. -Changing the development process in large-size institutions represents -an organizational disturbance which impacts on structure, culture, and -management practices \cite{nerur2015challenges}. As a result, government and -academia have to harmonize their view to increasing the chances of success in -projects with tight deadlines and short budgets. +Poor project management is one of the causes of projects failures in the +government \cite{anthopoulos2016egovernment} which in turn grows into a +critical issue when government and academia combine efforts to develop an +e-government solution. Academia commonly works on cutting edge of technology +while the government is still relying on traditional techniques. Changing the +development process in large-size institutions represents an organizational +disturbance with impacts on structure, culture, and management practices +\cite{nerur2015challenges}. As a result, government and academia have to +harmonize their view to increasing the chances of success in projects with +tight deadlines and short budgets. -% TODO: Projetos de sl tem x características e muitas de suas práticas tem se mostrado válidas e que abrem precedentes para utilizar no contexto governo academia. Falar da influência do SL no projeto +An option for harmonizing different management approaches, it is bringing +procedures from Free Libre Open Source (FLOSS) ecosystems and agile. Open +communication, project modularity, the community of users, and fast response to +problems are just a few of the FLOSS ecosystem practices \cite{capiluppi, +warsta}. Individuals and interactions, Working software, Customer +collaboration, Responding to change \cite{beck} are the core of agile +development. The intersection between FLOSS and agile can harmonize different +process management and improves the cooperation of distinct teams. -In this work we investigate a set of practices from a 30-month +In this work, we investigate a set of practices from a 30-month government-academia project that helped to harmonize the differences between government and academia management cultures. We trace the best practices based -on open source ecosystems and agile methodologies. Finally, we validate their -benefits by collecting data from the main project repository and by surveying -the project participant points of view. - +on FLOSS ecosystems and agile methodology. Finally, we validate the set of +methods extracted from the project by collecting data from the project + repository and by surveying the project participant points of view. diff --git a/oss2018/content/02-relatedwork.tex b/oss2018/content/02-relatedwork.tex index 911073a..100a35f 100644 --- a/oss2018/content/02-relatedwork.tex +++ b/oss2018/content/02-relatedwork.tex @@ -1,61 +1,57 @@ \section{Related work} \label{sec:relatedwork} -% TODO: -%O related work está bem montado. Contudo, eu senti falta de falar sobre -%software livre. A adoção dele ou de suas práticas. Se não existe ainda esse -%estudo, então essa seria uma bela colaboração da nossa parte e deveria ser -%evidênciada no último parágrafo. IMO isso é importante uma vez que é a nossa -%chance de por a parte de FLOSS que sempre defendemos, em adição a conferência é -%sobre FLOSS e talvez possam dizer que a gente não se 'enquadra' na conferência. -%Não acho que precisamos tirar a parte 'agile', mas precisamos ser mais conciso -%sobre isso - -%Sugestão do Fabio: Colocar referências de trabalho que conseguiram conciliar -%ou que reportam dificuldade em conciliar ou aplicar processos de gerenciamento -%em um projeto de colaboração - +% TODO: Verificar se não vale a pena citar os fatores que o Strode descobriu. +% Eu acho que deixaria a frase mais completa Discussions on how to introduce new management methods into an organization are -present in several papers. Nerur et al. identify the critical issues that involve -migrating from traditional to agile by comparing main practices of the two +present in several papers. Nerur et al. recognized critical issues concerning +the migration from traditional to agile by comparing practices of both methodologies \cite{nerur2015challenges}. 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. -investigate the correlation between adoption of agile methodologies and -organizational culture \cite{impactOfOrganizationalCulture}. They evaluate the -perception of organizational culture and the use of agile practices in nine -software development projects, identifying organizational culture factors that -are correlated to the implementation of agile methods. +investigated the relationship between the adoption of agile methodologies and +organizational culture \cite{impactOfOrganizationalCulture} by evaluating nine +projects. They identified a set of factors directly linked to the agile +methods. Some works also discuss how academia can collaborate with the industry in the -management of software projects. Chookittikul et al. evaluates the increasing -use of the agile methods by software development organizations in Thailand and -suggests universities create curricula which develop in their undergraduate -students' practical skills required by industry (mainly agile practices) to -encourage the software industry growth in the region \cite{cho2011gap}. -Sandberg et al. report the use of Scrum in a collaborative research -consortium between industry and academia (involving ten industry partners and -five universities in Sweden) \cite{sandberg2017iacollaboration}. - -New variables arise when a different approach to project management is -introduced to complex and large-scale organizations, such as the public -administration. Alleman et al. describe a production deployment for the US -government, focus on describing the methodology applied to address long-term -planning and value estimation \cite{alleman2003making}. Agile methods -application in the Brazilian public sector are approached by Melo et al. \cite{melo2013agileBr} and De -Sousa et al. \cite{de2016using}, both are experiences limited -to pilot projects. Not production-ready one that will provide more accurate -data with the real world. - -This paper differentiates itself from others by describing a production level -software development collaboration between government and academia, -analyzing differences in the development process and administrative issues of -the two organizations, and evidencing empirical practices that harmonized the -interactions and satisfied the development and management process of both -sides. - -% 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 +management of software projects. Chookittikul et al. evaluated the increasing +use of the agile techniques in the software development companies in Thailand. +The authors suggested that universities should create curricula which develop +in their undergraduate student's practical skills required by industry (mainly +agile practices) to promote growth in the local software business \cite{cho2011gap}. +Sandberg et al. report the use of Scrum in a collaborative research consortium +between industry and academia (involving ten industry partners and five +universities in Sweden) \cite{sandberg2017iacollaboration}. + +% TODO: Eu tirei várias coisas, que ao meu ver não estavam agregando. Verificar +% se não mudei o significado de algo +Complex and large-scale organizations, such as the public administration, have +to deal with multiple project variables. Alleman et al. describe a production +deployment for the US government, focus on the methodology applied to address +long-term planning and value estimation \cite{alleman2003making}. Agile +methods application in the Brazilian public sector are approached by Melo et +al. \cite{melo2013agileBr} and De Sousa et al. \cite{de2016using}, both are +experiences limited to pilot projects. + +% TODO: Parágrafo novo, vale a pena dar uma olhada +Several works tried to highlight the FLOSS practices, while others attempted to +determine the relationship between the FLOSS practices and agile methods. +Capiluppi et al. examined about 400 projects to find FLOSS project properties +\cite{capiluppi}. In their work, they extracted generic characterization +(project size, age, license, and programming language), analyzed the average +number of people involved in the project, the community of user, and +documentation characteristics. Warsta et al. found differences and similarities +between agile development and FLOSS practices \cite{warsta}. The authors argued +that FLOSS development may differ from agile by philosophical and economic +perspective, on the other hand, both shares the definition of work. Finally, +Eric Raymond describes many of his experience and decisions in his work with +FLOSS communities \cite{raymond}, this report has many intersections with the +agile manifesto. + +% TODO: Mudei consideravelmente esse parágrafo +This paper distinguishes itself from others by studying a software created in +collaboration between government and academia. We extracted empirical practices +that helped to harmonize the interactions between two different development +process and satisfied the management process of both sides. We analyzed these +methods from the FLOSS an agile perspective. diff --git a/oss2018/spb-oss-2018.bib b/oss2018/spb-oss-2018.bib index ade5d2e..56dfeca 100644 --- a/oss2018/spb-oss-2018.bib +++ b/oss2018/spb-oss-2018.bib @@ -1,39 +1,39 @@ -@article{anthopoulos2016egovernment, - title={Why e-government projects fail? An analysis of the Healthcare. gov website}, - author={Anthopoulos, Leonidas and Reddick, Christopher G and Giannakidou, Irene and Mavridis, Nikolaos}, - journal={Government Information Quarterly}, - volume={33}, - number={1}, - pages={161--173}, - year={2016}, - publisher={Elsevier} -} + @article{anthopoulos2016egovernment, + title={Why e-government projects fail? An analysis of the Healthcare. gov website}, + author={Anthopoulos, Leonidas and Reddick, Christopher G and Giannakidou, Irene and Mavridis, Nikolaos}, + journal={Government Information Quarterly}, + volume={33}, + number={1}, + pages={161--173}, + year={2016}, + publisher={Elsevier} + } -@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{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} + } -@article{goldfinch2007pessimism, - ISSN={00333352, 15406210}, - URL={http://www.jstor.org/stable/4624644}, - author={Shaun Goldfinch}, - journal={Public Administration Review}, - number={5}, + @article{goldfinch2007pessimism, + ISSN={00333352, 15406210}, + URL={http://www.jstor.org/stable/4624644}, + author={Shaun Goldfinch}, + journal={Public Administration Review}, + number={5}, pages={917-929}, publisher={[American Society for Public Administration, Wiley]}, title={Pessimism, Computer Failure, and Information Systems Development in the Public Sector}, @@ -224,3 +224,38 @@ organization={IEEE} } +@inproceedings{capiluppi, + title={Characteristics of open source projects}, + author={Capiluppi, Andrea and Lago, Patricia and Morisio, Maurizio}, + booktitle={Software Maintenance and Reengineering, 2003. Proceedings. Seventh European Conference on}, + pages={317--327}, + year={2003}, + organization={IEEE} +} + +@inproceedings{warsta, + title={Is open source software development essentially an agile method}, + author={Warsta, Juhani and Abrahamsson, Pekka}, + booktitle={Proceedings of the 3rd Workshop on Open Source Software Engineering}, + pages={143--147}, + year={2003} +} + +@article{beck, + title={Manifesto for Agile Software Development. Agile Alliance (2001)}, + author={Beck, Kent and Beedle, M and Bennekum, A and others}, + journal={Retrieved June}, + volume={14}, + year={2010} +} + +@article{raymond, + title={The cathedral and the bazaar}, + author={Raymond, Eric}, + journal={Philosophy \& Technology}, + volume={12}, + number={3}, + pages={23}, + year={1999}, + publisher={Springer} +} -- libgit2 0.21.2