Um estudo sobre a rela??o da ado??o do m?todo ?gil SCRUM com a produtividade em equipes de desenvolvimento de software

• Ano de defesa: 2017
• Autor(a) principal: Bellenzier, Marina
• Orientador(a): Prikladnicki, Rafael
• Tipo de documento: Dissertação
• Tipo de acesso: Acesso aberto
• Idioma: por
• Instituição de defesa: Pontif?cia Universidade Cat?lica do Rio Grande do Sul
• Programa de Pós-Graduação: Programa de P?s-Gradua??o em Ci?ncia da Computa??o
• Departamento: Faculdade de Inform?tica
• País: Brasil
• Palavras-chave em Português: M?todo ?gil; Produtividade; OKR; SCRUM
• Área do conhecimento CNPq: CIENCIA DA COMPUTACAO::TEORIA DA COMPUTACAO
• Link de acesso: http://tede2.pucrs.br/tede2/handle/tede/7746

New technology deployment projects should understand the immediate impact this change has on the professionals involved in the work process. In the first months of a technological change, it is possible to identify a certain resistance and even some conflicts that affect the levels of productivity of the teams. The objective of this work was to understand the relation of productivity with the changes in the work characteristics of teams that begin to adopt the SCRUM agile method for software development and to propose practices that help to reduce the learning curve and to improve productivity. Through the understanding of the Tuckman model, which describes the five stages of a team development: formation, confusion / conflicts, normalization, performance, and disintegration, a case study was carried out with a team that started to adopt SCRUM and identified the relationship between productivity and the phases described by Tuckman. In this sense, a field research was necessary to find practices that could help teams to increase their productivity during the confusion phase described by Tuckman. Through the preparation of a preliminary proposal, and an it?s preliminary evaluation in a Focus Group activity, this research presents a proposal to use the OKR technique (Objectives and Key-Results) along with SCRUM with the objective of assisting software team development, to concentration in the phase of confusion / conflicts.