What should be done when there is no Product Owner? a study about this role absence
The Agile Project Management approach innovates to stablish new management practices, such as iterative planning, product vision and client involvement in the project development. The client involvement happens through Product Owner’s role. Nevertheless, how teams can procced when this professional...
| Autores: | , |
|---|---|
| Tipo de recurso: | artículo |
| Estado: | Versión publicada |
| Fecha de publicación: | 2022 |
| País: | Brasil |
| Institución: | Universidade Nove de Julho (UNINOVE) |
| Repositorio: | Revista Gestão e Projetos (GeP) |
| Idioma: | portugués |
| OAI Identifier: | oai:https://periodicos.uninove.br:article/22209 |
| Acceso en línea: | https://periodicos.uninove.br/gep/article/view/22209 |
| Access Level: | acceso abierto |
| Palabra clave: | Product Owner; Agility; Scrum master; Responsibilities; Project management; Agile Product Owner; Agilidade; Scrum master; Responsabilidades; Gerenciamento de projetos; Ágil. |
| Sumario: | The Agile Project Management approach innovates to stablish new management practices, such as iterative planning, product vision and client involvement in the project development. The client involvement happens through Product Owner’s role. Nevertheless, how teams can procced when this professional is not present or is not committed? How are their tasks assigned to other team roles? Are those tasks accomplished? What is the impact? In this context, this article analyses teams that don’t have this specific role of Product Owner. A review of the tasks designated by the literature for this role was held and, based on these results, a case study was conducted in teams that make use of agile management practices without the presence of the Product Owner. The work identified that, in the cases that were studied, the project with the low involved Product Owner had more impairment than a project in which there was no one formally defined as Product Owner, being distributed to other professionals. It also identified a possible proposal that Scrum Master may become overloaded when the Product Owner does not do its tasks as expected. Finally, despite the understanding of the importance and need of this role, it was possible to realize that the projects studied were successful for customers even without the presence of the Product Owner. Future studies are recommended that can generalize those results by identifying the best way to assign Product Owner’s tasks in absence situations. |
|---|