O valor percebido pelo cliente na gestão de projetos de software, utilizando o Framework Scrum

Reginaldo Aparecido Carneiro; Mauro Luiz Martens; Vanessa Mesquita Blas Garcia; Ernesto D. R. Santibañez Gonzalez

doi:10.5585/gep.v13i3.22991

Autores

Reginaldo Aparecido Carneiro Universidade Cesumar – UniCesumar https://orcid.org/0000-0001-8477-8773
Mauro Luiz Martens Universidade Paulista – UNIP e Universidade de São Paulo – POLI USP https://orcid.org/0000-0003-1242-8795
Vanessa Mesquita Blas Garcia Universidade Nove de Julho – UNINOVE https://orcid.org/0000-0002-5914-0425
Ernesto D. R. Santibañez Gonzalez Universidade Paulista - UNIP / Universidade de Talca / Chile https://orcid.org/0000-0002-5753-8325

DOI:

https://doi.org/10.5585/gep.v13i3.22991

Palavras-chave:

Gestão ágil de projetos, Valor percebido, Cliente, Framework Scrum, Ágil, Product owner, Software.

Resumo

A qualidade e o sucesso de um projeto dependem da forma como se capta as necessidades e as expectativas do cliente. Dessa forma, o objetivo geral deste artigo incide sobre a verificação de como o valor percebido pelo cliente é considerado na entrega de um projeto a partir da utilização do framework ágil Scrum. Como metodologia, foi utilizada um estudo de caso a partir da análise de uma empresa brasileira atuante na área de software, localizada no interior do estado do Paraná, na cidade de Maringá. As informações foram coletadas com base em entrevista semiestruturada, realizada in loco a partir de um protocolo de pesquisa contendo 14 questões abertas, confrontando a referida entrevista com a literatura científica do assunto. O estudo realizado permitiu levantar práticas executadas pela empresa objeto de estudo que variam de acordo com a literatura, tais como o atendimento dos princípios comuns das metodologias ágeis, e a utilização eficiente dos pilares do framework Scrum. Em contrapartida, percebeu-se algumas divergências junto ao atendimento do cliente, no que tange à comunicação com o solicitante do projeto, pois, além do Product Owner (PO), outros envolvidos com o projeto também podem, a qualquer momento, entrar em contato com o cliente. Com isso, surge a possibilidade desta atitude promover ruídos na comunicação entre os envolvidos, o que pode resultar em um projeto que não atenda rigorosamente ao valor percebido pelo cliente que o requisitou.

Referências

Abrahamsson, P.; Oza, N.; & Siponen, M. T. (2010). Agile Software Development Methods: A Comparative Review 1. In: Agile software development. Springer Berlin Heidelberg, 31-59. https://doi.org/10.1007/978-3-642-12575-1_3

Abrahamsson, P; Conboy, K; & Wang, X. (2009). ‘Lots done, more to do’: the current state of agile systems development research. European Journal of Information Systems, 18(4), 281-284. https://doi.org/10.1057/ejis.2009.2

Abrahamsson, P; Salo, O.; Ronkainen, J.; & Warsta, J. (2002). Agile software development methods: Review and analysis. https://doi.org/10.48550/arXiv.1709.08439.

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 (JTEC), 9(1-2), 53-56.

Antlova, K. (2014). Agile Approach in the Project Management of the Czech Companies. Procedia Technology, 16 (2014), 929 – 933. https://doi.org/10.1016/j.protcy.2014.10.045

Asnawi, A. L.; Gravell, A. M.; & Wills, G. B. (2012). Emergence of agile methods: perceptions from software practitioners in Malaysia. In: AGILE India, 2012. IEEE, 2012. https://doi.org/10.1109/AgileIndia.2012.14

Arefazar, Y., Nazari, A., Hafezi, M. R., & Maghool, S. A. H. (2022). Prioritizing agile project management strategies as a change management tool in construction projects. International Journal of Construction Management, 22(4), 678-689. https://doi.org/10.1080/15623599.2019.1644757

Augustine, S. (2005). Managing Agile Projects. Virginia: Prentice Hall PTR.

Bambauer-Sachse, S., & Helbling, T. (2021). Customer satisfaction with business services: is agile better? Journal of Business & Industrial Marketing. https://doi.org/10.1108/jbim-04-2020-0221

Beck, K., Beedle, M., Van Bennekum, A., Cockburn, A., Cunningham, W., Fowler, M.,

Grenning, J., Highsmith, J., Hunt, A., Jeffries, R., Kern, J., Marick, B., Martin, R. C., Mellor, S., Schwaber, K., Sutherland, J., & Thomas, D. (2001). Manifesto for agile software development.

Beck, K. (2000). Extreme programming explained: embrace change. Addison-Wesley professional.

Belsis, P.; Koutoumanos, A.; & Sgouropoulou, C. (2014). PBURC: a patterns-based, unsupervised requirements clustering framework for distributed agile software development. Requirements Engineering, 19(2), 213-225. https://doi.org/10.1007/s00766-013-0172-9

Bergadano, F.; Bosio, G.; & Spagnolo, S. (2014). Supporting collaboration between customers and developers: a framework for distributed, agile software development. International Journal of Distributed Systems and Technologies, 5(2), 1-16. https://doi.org/10.4018/ijdst.2014040101

Cervone, H. (2011). Understanding agile project management methods using Scrum. OCLC Systems & Services: International digital library perspectives, 27, 18-22. https://doi.org/10.1108/10650751111106528

Conboy, K. (2009). Agility from first principles: reconstructing the concept of agility in information systems development. Information Systems Research, 20(3), 329-354. https://doi.org/10.1287/isre.1090.0236

Conforto, E. C., Salum, F., Amaral, D. C., Da Silva, S. L., & De Almeida, L. F. M. (2014). Can agile project management be adopted by industries other than software development? Project Management Journal, 45(3), 21-34. https://doi.org/10.1002/pmj.21410

Curcio, K., Navarro, T., Malucelli, A., & Reinehr, S. (2018). Requirements engineering: A systematic mapping study in agile software development. Journal of Systems and Software, 139, 32-50. https://doi.org/10.1016/j.jss.2018.01.036

De Souza Lopes, S., de Souza, R. C. G., de Godoi Contessoto, A., de Oliveira, A. L., & Braga, R. T. V. (2022). Automated Support for Risk Management in Scrum Agile Projects. In International Conference on Enterprise Information Systems (pp. 236-255). Springer, Cham.

De Souza Lopes, S., de Souza, R. C. G., Contessoto, A. D. G., de Oliveira, A. L., & Braga, R. T. V. (2021, April). A Risk Management Framework for Scrum Projects. In ICEIS (2) (pp. 30-40). https://doi.org/10.5220/0010448300300040

Devmedia (2016). Agile Development: XP e Scrum em uma Abordagem Comparativa. Disponível em: http://www.devmedia.com.br/agile-development-xp-e-scrum-em-uma-abordagem-comparativa/30808.

Elghariani, K., & Kama, N. (2016). Review on Agile requirements engineering challenges. In 2016 3rd International conference on computer and information sciences (ICCOINS) (pp. 507-512). IEEE. https://doi.org/10.1109/ICCOINS.2016.7783267

El-Najar, T., Ahmad, I., & Alkandari, M. (2019). Easycomm: A Framework and Tool to Solve Client Communication Problem in Agile Development. IAENG International Journal of Computer Science, 46(1).

Fernandez, D. J.; & Fernandez, J. D. (2008). Agile project management-Agilism versus traditional approaches. Journal of Computer Information Systems, 49(2), 10-17. https://doi.org/10.1080/08874417.2009.11646044

Ferreira, C., & Cohen, J. (2008, October). Agile systems development and stakeholder satisfaction: a South African empirical study. In Proceedings of the 2008 annual research conference of the South African Institute of Computer Scientists and Information Technologists on IT research in developing countries: riding the wave of technology (pp. 48-55).

Fitzgerald, B.; Hartnett, G.; & Conboy, K. (2006). Customising agile methods to software practices at Intel Shannon. European Journal of Information Systems, 15(2), 200-213. https://doi.org/10.1057/palgrave.ejis.3000605

Ghani, I., Bello, M., & Bagiwa, I. L. (2015). A survey-based analysis of agile adoption on performances of IT organizations. Journal of Internet Computing and Services, 16(5), 87-92. http://dx.doi.org/10.7472/jksii.2015.16.5.87

Goode, W.; & Hatt, P. (1975). Métodos em pesquisa social. 5ª ed. São Paulo: Ed. Nacional.

Grapenthin, S.; Poggel, S.; Book, M.; & Gruhn, V. (2015). Improving task breakdown comprehensiveness in agile projects with an Interaction Room. Information and Software Technology, 67, 254-264. https://doi.org/10.1016/j.infsof.2015.07.008

Guo, C., Kulviwat, S., Zhu, J., & Wang, Y. J. (2019). Competing in an emerging market: antecedents and consequences of market orientation and the role of environmental factors. Journal of Strategic Marketing, 27(3), 248-267. https://doi.org/10.1080/0965254X.2017.1411386

Hannay, J. E., Benestad, H. C., & Strand, K. (2017). Benefit points: the best part of the story. IEEE Software, 34(3), 73-85. DOI:10.1109/MS.2017.66

Highsmith, J. (2004). Agile Project Management: creating innovative products. Boston: Addison-Wesley.

Inayat, I., Salim, S. S., Marczak, S., Daneva, M., & Shamshirband, S. (2015). A systematic literature review on agile requirements engineering practices and challenges. Computers in human behavior, 51, 915-929. https://doi.org/10.1016/j.chb.2014.10.046

Kevin Sungkur, R.; & Ramasawmy, M. (2014). Knowledge4Scrum, a novel knowledge management tool for agile distributed teams. Vine, 44(3), 394-419.

Kurniawan, R., Budiastuti, D., Hamsal, M., & Kosasih, W. (2020). The impact of balanced agile project management on firm performance: the mediating role of market orientation and strategic agility. Review of International Business and Strategy. https://doi.org/10.1108/RIBS-03-2020-0022

Lima, A. P. R., & Amaral, D. C. (2022). O que fazer quando não há Product Owner? Um estudo sobre a ausência desse papel. Revista de Gestão e Projetos (GeP), 13(2), 38-65. https://doi.org/10.5585/gep.v13i2.22209.

Massari, V. (2014). Gerenciamento Ágil de Projetos. Rio de Janeiro: Brasport.

Matook, S., & Maruping, L. M. (2014). A competency model for customer representatives in agile software development projects. MIS Quarterly Executive, 13(2).

Mchugh, O.; Conboy, K.; & Lang, M. (2012). Agile practices: The impact on trust in software project teams. Ieee Software, 29(3), 71-76. https://doi.org/10.1109/MS.2011.118

Moe, N. B.; Dingsøyr, T.; & Dybå, T. (2009). Overcoming barriers to self-management in software teams. IEEE software, 26(6), 20-26.

Nerur, S.; Mahapatra, R.; & Mangalaraj, G. (2005). Challenges of migrating to agile methodologies. Communications of the ACM, 48(5), 72-78.

Niemi-Grundström, M. (2014). Developing, evaluating and managing library with agile methods. Library Management, 35(6/7), 481-485. https://doi.org/10.1108/LM-02-2014-0022

Oliveira, E.; & Lima, R. (2012). Estado da arte sobre o uso do Scrum em ambientes de desenvolvimento distribuído de software. Revista de Sistemas e Computação-RSC, 1(2).

Paasivaara, M.; Durasiewicz, S.; & Lassenius, C. (2008). Using scrum in a globally distributed project: a case study. Software Process: Improvement and Practice, 13(6), 527-544. https://doi.org/10.1002/spip.402

Parker, D. W., Kunde, R., & Zeppetella, L. (2017). Exploring communication in project-based interventions. International Journal of Productivity and Performance Management, 66(2,), 146-179. https://doi.org/10.1108/IJPPM-07-2015-0099

Pearce, C. L. (2004). The future of leadership: Combining vertical and shared leadership to transform knowledge work. The Academy of Management Executive, 18(1), 47-57. https://doi.org/10.5465/AME.2004.12690298

Pichler, R. (2010). Agile product management with scrum: creating products that customers love. Addison-Wesley Professional.

Pikkarainen, M.; Haikara, J.; Salo, O.; Abrahamsson, P.; & Still, J. (2008). The impact of agile practices on communication in software development. Empirical Software Engineering, 13(3), 303-337. https://doi.org/10.1007/s10664-008-9065-9

Rajan, E. R., & Santhosh, V. A. (2021). Adoption of Agile Methodology for improving it project perforMAnce. Serbian Journal of Management, 16(2). DOI:10.5937/sjm16-26854

Ramesh, B., Cao, L., & Baskerville, R. (2010). Agile requirements engineering practices and challenges: an empirical study. Information Systems Journal, 20(5), 449-480. https://doi.org/10.1111/j.1365-2575.2007.00259.x

Recker, J., Holten, R., Hummel, M., & Rosenkranz, C. (2017). How agile practices impact customer responsiveness and development success: A field study. Project Management Journal, 48(2), 99-121. https://doi.org/10.1177/875697281704800208

Richardson, R. J. (2017). Pesquisa social: métodos e técnicas. 4. ed. São Paulo: Atlas.

Schwaber, K.; & Sutherland, J. (2013). Guia do ScrumTM. Disponível em: http://www.scrumguides.org/docs/scrumguide/v1/Scrum-Guide-Portuguese-BR.pdf, 2022.

Schwaber, K. (2004). Agile project management with Scrum. Microsoft press.

Schwaber K, & Beedle M. (2010). Agile Software Development with Scrum. Prentice Hall: New York.

Seabra, C.; & Almeida, A. M. (2015). Project management on Multimedia Projects: preliminary results on communication, interaction and team work dynamics. Procedia Computer Science, 64, 816-823. https://doi.org/10.1016/j.procs.2015.08.633

Selim Senyurt, B., Basri Yuksel, H., Asilsamanci, E., & Ozkil, A. (2021, August). Turkuaz: The Modernization of an ERP Application with Agile Methodology in The Automotive Sector in Turkey. In 2021 The 11th International Conference on Information Communication and Management (pp. 1-10).

Serrador, P., & Pinto, J. K. (2015). Does Agile work? A quantitative analysis of agile project success. International Journal of Project Management, 33(5), 1040-1051. https://doi.org/10.1016/j.ijproman.2015.01.006

Shalloway, A.; Beaver, G.; & Trott, J. (2009). Lean-agile software development: achieving enterprise agility. Pearson Education.

Sommerville, I. (2007). Engenharia de Software. 8ª ed. São Paulo: Pearson.

Sutherland, J., & Schwaber, K. (2014). The Scrum Papers. Nuts, Bolts and Origins of an Agile Process.

Sverrisdottir, H.; Ingason, H.; & Jonasson, H. (2014). The role of the product owner in scrum-comparison between theory and practices. Procedia-Social and Behavioral Sciences. 119, 257-267. https://doi.org/10.1016/j.sbspro.2014.03.030

Thorgren, S., & Caiman, E. (2019). The role of psychological safety in implementing agile methods across cultures. Research-Technology Management, 62(2), 31-39. https://doi.org/10.1080/08956308.2019.1563436

Tsai, W. L., Chen, C. Y., & Chen, C. S. (2018). Snowman: Agile development method with institutionalized communication and documentation for capstone projects. Asia Pacific Management Review, 23(1), 12-19. https://doi.org/10.1016/j.apmrv.2017.01.002

Tseng, M.; & Du, X. (1998). Design by customers for mass customization products. CIRP Annals-Manufacturing Technology, 7(1), 103-106. DOI: 10.1007/978-0-85729-224-7_41

Van Waardenburg, G.; & Van Vliet, H. (2013). When agile meets the enterprise. Information and software technology, 55(12), 2154-2171. https://doi.org/10.1016/j.infsof.2013.07.012

Versionone (2020) 14th-Annual-State-of-Agile-Development-Survey. Disponível em: https://stateofagile.com/home#ufh-i-615706098-14th-annual-state-of-agile-report/7027494.

Wang, X., Conboy, K., & Pikkarainen, M. (2012). Assimilation of agile practices in use. Information Systems Journal, 22(6), 435-455. https://doi.org/10.1111/j.1365-2575.2011.00393.x

West, D.; Grant, T.; Gerish, M.; & D’Silva, D., (2010). Agile development: mainstream adoption has changed agility. Forrester Research, 2(1), 41.

Witell, L., Kowalkowski, C., Perks, H., Raddats, C., Schwabe, M., Benedettini, O., & Burton, J. (2020). Characterizing customer experience management in business markets. Journal of Business Research, 116, 420-430. https://doi.org/10.1016/j.jbusres.2019.08.050

Yin, R. K. (2005). Estudo de caso: planejamento e métodos. 3ª ed. Porto Alegre: Bookman.

Younas, M., Jawawi, D. N., Ghani, I., Fries, T., & Kazmi, R. (2018). Agile development in the cloud computing environment: A systematic review. Information and Software Technology, 103, 142-158. https://doi.org/10.1016/j.infsof.2018.06.014