Management of software development projects in Brazil using agile methods
Main Article Content
صندلی اداریAbstract
Downloads
Article Details
![Creative Commons License](http://i.creativecommons.org/l/by-nc-sa/4.0/88x31.png)
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
1. Proposal of Policy for Free Access Periodics
Authors whom publish in this magazine should agree to the following terms:
a. Authors should keep the copyrights and grant to the magazine the right of the first publication, with the work simultaneously permitted under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 that allows the sharing of the work with recognition of the authorship of the work and initial publication in this magazine.
b. Authors should have authorization for assuming additional contracts separately, for non-exclusive distribution of the version of the work published in this magazine (e.g.: to publish in an institutional repository or as book chapter), with recognition of authorship and initial publication in this magazine.
c. Authors should have permission and should be stimulated to publish and to distribute its work online (e.g.: in institutional repositories or its personal page) to any point before or during the publishing process, since this can generate productive alterations, as well as increasing the impact and the citation of the published work (See The Effect of Free Access).
Proposal of Policy for Periodic that offer Postponed Free Access
Authors whom publish in this magazine should agree to the following terms:
a. Authors should keep the copyrights and grant to the magazine the right of the first publication, with the work simultaneously permitted under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 [SPECIFY TIME HERE] after the publication, allowing the sharing of the work with recognition of the authorship of the work and initial publication in this magazine.
b. Authors should have authorization for assuming additional contracts separately, for non-exclusive distribution of the version of the work published in this magazine (e.g.: to publish in institutional repository or as book chapter), with recognition of authorship and initial publication in this magazine.
c. Authors should have permission and should be stimulated to publish and to distribute its work online (e.g.: in institutional repositories or its personal page) to any point before or during the publishing process, since this can generate productive alterations, as well as increasing the impact and the citation of the published work (See The Effect of Free Access).
d. They allow some kind of open dissemination. Authors can disseminate their articles in open access, but with specific conditions imposed by the editor that are related to:
Version of the article that can be deposited in the repository:
Pre-print: before being reviewed by pairs.
Post-print: once reviewed by pairs, which can be:
The version of the author that has been accepted for publication.
The editor's version, that is, the article published in the magazine.
At which point the article can be made accessible in an open manner: before it is published in the magazine, immediately afterwards or if a period of seizure is required, which can range from six months to several years.
Where to leave open: on the author's personal web page, only departmental websites, the repository of the institution, the file of the research funding agency, among others.
References
Abdalhamid, S., & Mishra, A. (2017). Adopting of Agile methods in Software Development Organizations: Systematic Mapping. Tem Journal-Technology Education Management Informatics, 6(4), 817-825.
Al-Aidaros, H. A. A., & Omar, M. (2017). Software project management approaches for monitoring work-in-progress: A review. Journal of Engineering and Applied Sciences, 12( 15), 3851-3857.
Al-Sakkaf, A. M., Hashim, N. L., & Omar, M. (2017). Using hierarchical cluster analysis to generate clusters of agile practices. Journal of Telecommunication, Electronic and Computer Engineering, 9(1-2), 53-56.
Beck, K. et al. (2001). Manifesto para Desenvolvimento Ágil de Software. Available at: http://agilemanifesto.org/iso/ptbr/manifesto.html, Accessed on 02 apr. 2017.
Bowen, J. P., Hinchey, M., Janicke, H., Ward, M., & Zedan, H. (2014). Formality, agility, security, and evolution in software development. Computer, 47(10), 86-89.
Chow, T., & Cao, D. B. (2008). A survey study of critical success factors in agile software projects. Journal of Systems and Software, 81(6), 961-971.
Dingsøyr, T., Moe, N. B., Fægri, T. E., & Seim, E. A. (2017). Exploring software development at the very large-scale: a revelatory case study and research agenda for agile method adaptation. Empirical Software Engineering, 25(1), 1-31.
Farid, A. B., Abd Elghany, A. S., & Helmy, Y. M. (2016). Implementing Project Management Category Process Areas of CMMI Version 1.3 Using Scrum Practices, and Assets. International Journal of Advanced Computer Science and Applications, 7(2), 243-252.
Gray, D. E. (2012). Pesquisa no Mundo Real. 2ª. Porto Alegre.
Guia Pmbok. (2013). 5 Edition - Portuguese. PMI.
Kulkarni, R. H., Padmanabham, P., Harshe. M., Baseer, K. K., & Patil, P. (2017). Investigating agile adaptation for project development. International Journal of Electrical and Computer Engineering, 7(3), 1278-1285.
Laanti, M. (2014). Characteristics and principles of scaled agile. Lecture Notes in Business Information Processing: Springer Verlag, 199, 9-20.
Lee, S., & Yong, H. S. (2017). Distributed agile: project management in a global environment. Empirical Software Engineering, 15(2), 204-217.
Mahnic, V., & Zabkar, N. (2012). Measuring Progress of Scrum-based Software Projects. Elektronika Ir Elektrotechnika, 18(8), 73-76.
Nuottila, J., Aaltonen, K., & Kujala, J. (2016). Challenges of adopting agile methods in a public organization. Ijispm-International Journal of Information Systems and Project Management, 4(3), 65-85.
Odzaly, E. E., Greer, D., & Stewart, D. (2018). Agile risk management using software agents. Journal of Ambient Intelligence and Humanized Computing, 9(3), 823-841.
Papatheocharous, E., Andreou, A. S. (2014). Empirical evidence and state of practice of software agile teams. Journal of Software-Evolution and Process, 26(9), 855-866.
PMI - Project Management Institute. (2017). Agile Practice Guide.
Pressman, R. S. (2016). Engenharia de Software: Uma abordagem profissional. 8ª. Rio de Janeiro: Editora McGraw-Hill.
SEBRAE (2013). Anuário do trabalho na micro e pequena empresa), 17. Available at: https://m.sebrae.com.br/Sebrae/Portal%20Sebrae/UFs/SP/Pesquisas/MPE_conceito_empregados.pdf. Accessed on 12 dez. 2017.
Sheffield, J., & Lemétayer, J. (2013). Factors associated with the software development agility of successful projects. International Journal of Project Management, 31(3), 459–472.
Sundararajan, S., Bhasi, M., & Vijayaraghavan, P. K. (2014).. Case study on risk management practice in large offshore-outsourced Agile software projects. IET Software, 8(6), 245-257.
Surdu, J., & Parsons, D. J. (2006). Army simulation program balances agile and traditional methods with success. CrossTalk, 19(4), 4-8.
Sutharshan, A. (2011). Enhancing Agile methods for multi-cultural software project teams. Modern Applied Science, 5(1), 12-22.
Tripp, J. F., Riemenschneider, C., & Thatcher, J. B. (2016). Job Satisfaction in Agile Development Teams: Agile Development as Work Redesign. Journal of the Association for Information Systems, 17(4), 267-307.
Vargas, L. M. (2016). Project Agile Management for Software Development: A Comparative Study on The Applicability of Scrum Together With Pmbok and / or Prince2. Revista de Gestao e Projetos, 7(3), 48-60.
Wautelet, Y., & Kolp, M. (2012). e-SPM: An Online Software Project Management Game. International Journal of Engineering Education, 28(6), 316-1325.