1 Introduction
2 Related Work
3 Research Method
3.1 Study Context and Research Setting
3.2 Data Collection and Analysis
4 Results
4.1 Continuous Product Development vs. Cross-Team Project
Context of the continuous product development | Context of cross-team project |
---|---|
Informal risk management by agile approach | Formal risk management in the responsibility of dedicated project manager |
Agile practices like daily standups, review meetings, and retrospectives promote a transparent management of risks | Explicit clarification of risk-related conditions and escalation instances during the project setup |
Regular exchange among teams on best practices in risk management | Standardized approach for identification, management, and evaluation of risks, based on experience from previous, larger projects |
Regular exchange with relevant stakeholders on project risks |
4.2 Gaps and Measurements Related to Risk Management
Context | Continuous product development | Cross-team project |
---|---|---|
Responsible for risks | Production lead, triade, team | Cross-team project manager, leading team |
Identified gaps | For this context, informal risk management has been assessed as sufficient. | 1. Clear, coordinated responsibility for risks is often lacking 2. Clear, coordinated responsibility for the implementation of measures is often lacking 3. Escalation instance for risks is unclear 4. Transparency with regard to risks from the perspective of the teams is often not given 5. Information flow at the project intersection continuous product development requires optimization |
Measures | Best practices workshop on internal team risks | a) Optimization interface cross-team project - continuous product development (improves Gaps 1, 2, 4, 5) b) Optimization tooling for project management, and especially for risk management (improves Gaps 1, 2, 4, 5) c) Optimization project setup and management (improves Gaps 1, 2, 3) |