Loading...
Publication
Mapping Risk Management Practices for Scrum Framework
| Name: | Description: | Size: | Format: | |
|---|---|---|---|---|
| 2.15 MB | Adobe PDF |
Authors
Advisor(s)
Abstract(s)
A gestão eficaz do risco é essencial para o sucesso dos projectos de desenvolvimento de software que utilizam metodologias ágeis. Este estudo analisa as práticas de gestão de risco no método Scrum, comparando-as com as abordagens tradicionais recomendadas pelo Guia PMBOK®. Através de uma revisão da literatura sobre o estado atual do conhecimento e de um questionário aplicado a 57 profissionais, analisámos as práticas de gestão de risco na framework Scrum e as ferramentas utilizadas ao longo do ciclo de vida do Scrum. Identificamos práticas no Scrum que podem ser vistas como equivalentes às práticas tradicionais de gestão de projetos do Guia PMBOK®.
Os resultados indicam que ferramentas como Categorização de Risco, Lista de Verificação e Análise de Causa Raiz são altamente valorizadas, sendo escolhidas por 67% dos participantes do estudo. A adoção de práticas adicionais do Guia PMBOK® pode ser desnecessária, uma vez que eventos e artefactos específicos do Scrum, como o Sprint Planning, Product Backlog e Sprint Retrospective, são considerados momentos críticos para identificar, analisar e responder aos riscos.
Este estudo oferece perspectivas práticas para as equipas de desenvolvimento de software e contribui para o conhecimento da gestão de projectos de software, salientando a importância da análise qualitativa e quantitativa dos riscos durante o Sprint Planning, para além da necessidade de um julgamento especializado e da análise de dados para decisões informadas. Compreender as práticas de gestão de software e para o conhecimento em gestão de projetos de software.
Effective risk management is essential to the success of software development projects using agile methodologies. This study examines risk management practices in the Scrum method, comparing them with the traditional approaches recommended by the PMBOK Guide®. Through a literature review on the current state of knowledge and a questionnaire applied to 57 professionals, we analysed risk management practices in the Scrum framework and the tools used throughout the Scrum lifecycle. We identified practices in Scrum that can be seen as equivalent to the traditional project management practices of the PMBOK Guide®. The results indicate that tools such as Risk Categorisation, Prompt List and Root Cause Analysis are highly valued, being chosen by 67% of the study participants. Adopting additional practices from the PMBOK Guide® may be unnecessary, as specific Scrum events and artefacts, such as Sprint Planning, Product Backlog and Sprint Retrospective, are considered critical moments for identifying, analysing, and responding to risks. This study offers practical insights for software development teams and contributes to software project management knowledge by emphasising the importance of qualitative and quantitative risk analysis during Sprint Planning, in addition to the need for expert judgement and data analysis for informed decisions. Understanding software management practices and knowledge of software project management.
Effective risk management is essential to the success of software development projects using agile methodologies. This study examines risk management practices in the Scrum method, comparing them with the traditional approaches recommended by the PMBOK Guide®. Through a literature review on the current state of knowledge and a questionnaire applied to 57 professionals, we analysed risk management practices in the Scrum framework and the tools used throughout the Scrum lifecycle. We identified practices in Scrum that can be seen as equivalent to the traditional project management practices of the PMBOK Guide®. The results indicate that tools such as Risk Categorisation, Prompt List and Root Cause Analysis are highly valued, being chosen by 67% of the study participants. Adopting additional practices from the PMBOK Guide® may be unnecessary, as specific Scrum events and artefacts, such as Sprint Planning, Product Backlog and Sprint Retrospective, are considered critical moments for identifying, analysing, and responding to risks. This study offers practical insights for software development teams and contributes to software project management knowledge by emphasising the importance of qualitative and quantitative risk analysis during Sprint Planning, in addition to the need for expert judgement and data analysis for informed decisions. Understanding software management practices and knowledge of software project management.
Description
Keywords
Project Management Risk Management Software Development Agile Methodologies Scrum