As a result of global networking, software development projects are carried out in cooperation with foreign specialists. This increases efficiency, but also increases the probability of personnel, cultural and legal risks. The software industry is highly dynamic and the market situation is changing due to the rapid development of new technologies.
To complete projects efficiently, companies rely on agile development procedures such as Scrum. Although Scrum is not part of the project management procedures, it takes over some points from classic project management: work packages must be prioritized, estimated and planned for the individual sprints. Scrum has few risk management approaches, which means that gaps can be identified, e.g. risks due to missing fixed prices, planning reliability. Thus, software vendors are in the dilemma of having to balance the pace of product development and product quality while considering the risks. This paper provides an exemplary elaboration on how Scrum can be expanded with little time and cost input through risk management.
Table of Contents
1. INTRODUCTION
2. THEORETICAL BASICS
2.1 Definition of "risk" and "risk management"
2.2 Project Risk Management Process
2.3 Categorization of risks
2.4 Risk management in project procedure models
3. THE RISK MANAGEMENT APPROACHES FOR SCRUM
3.1 Current point of view and problem description
3.2 Practical relevance
3.3 Methods and tools
3.3.1 Risk identification tools
3.3.2 Risk assessment tools
3.3.3 Distribution of roles
3.3.4 Documentation
3.4 Implementation phase
4. CONCLUSION AND OUTLOOK
Objectives and Topics
This thesis aims to demonstrate how risk management can be effectively integrated into Scrum-based software development projects in a medium-sized international company, specifically focusing on role allocation, framework supplementation, and risk assessment without sacrificing agility.
- Theoretical foundations of risk management in IT projects.
- Methods for risk identification and qualitative assessment.
- Practical integration of risk management into Scrum ceremonies and artifacts.
- Addressing cultural and communication challenges in international teams.
Excerpt from the Book
3.4 Implementation phase
Product Owner, Scrum Master and the team discuss the project goals, additional tasks for role allocation and documentation changes. The sprint is set to 3 weeks to get fast results and error verification. It is decided to adjust the length of the next sprint depending on the risk: the higher the risk values, the shorter the sprint. Since there is no detailed documentation from previous projects, the employees should provide subjective assessments based on their own experience. A list has been compiled and presented to the employees. Other project-related risks are identified using the "brainwriting" method and recorded on the list. Each risk is assigned a number and an occurrence indicator is added.
Summary of Chapters
1. INTRODUCTION: This chapter defines the scope of the thesis, which investigates supplementing Scrum-based projects with risk management in a medium-sized international company.
2. THEORETICAL BASICS: This section covers definitions of risk and risk management, outlines the cyclical nature of the risk management process, discusses various risk categories, and examines risk management within project procedure models.
3. THE RISK MANAGEMENT APPROACHES FOR SCRUM: This chapter presents the core practical application, including the problem description, relevance, specific identification/assessment methods, role distribution, and documentation strategies implemented in a case study.
4. CONCLUSION AND OUTLOOK: This chapter summarizes the results of the thesis, acknowledges limitations, and provides suggestions for further research into integrating risk management with agile frameworks.
Keywords
Scrum, Risk Management, Software Development, Agile, Risk Identification, Risk Assessment, Project Management, Role Allocation, Documentation, Scrum Master, Product Owner, International Projects, Risk Matrix, Brainwriting, Process Models
Frequently Asked Questions
What is the primary focus of this thesis?
The thesis focuses on integrating risk management into Scrum-based software development projects, specifically tailored for medium-sized international companies.
What are the central themes of the work?
The central themes include agile software development, risk management processes (identification and assessment), Scrum framework adjustments, and managing intercultural communication in projects.
What is the main objective or research question?
The goal is to demonstrate how Scrum can be supplemented with risk management approaches—specifically regarding roles, documentation, and risk assessment—while maintaining project agility.
Which scientific method is applied?
The author uses a constructed case study approach to demonstrate the implementation of risk management strategies within a Scrum-based project environment.
What is covered in the main section of the paper?
The main section details the initial problem description, practical relevance, specific tools like brainwriting and risk matrices, the distribution of roles among team members, and documentation strategies.
What are the key terms that characterize this work?
Key terms include Scrum, Risk Management, Software Development, Agile, Risk Identification, Risk Assessment, and Project Management.
How are cultural differences addressed in the proposed risk management?
The author suggests using brainwriting and moderated video conferences to overcome cultural power distance and communication gaps, allowing all team members to contribute equally.
Why is the "classic" project manager role considered unsuitable for Scrum?
The author argues that a traditional project manager role can destroy the hierarchical structure of Scrum and is unable to effectively control the process within the very short sprint cycles.
How is the "earned value" concept integrated into Scrum?
The author proposes adding "earned value" to the burndown chart to ensure that customer and market risks remain visible to the entire development team.
- Arbeit zitieren
- Larissa Petersen (Autor:in), 2017, Risk management of projects. Theoretical foundations and approaches for Scrum, München, GRIN Verlag, https://www.grin.com/document/954671
