Collective Risk Management in Software Projects

Effective risk management in software development projects requires business, product, and technical leaders to step beyond their individual domains and actively engage in the uncomfortable, shared space of collective risk management.

Risk management demands continuous collaboration, trade-offs, the courage and safety to speak up, and a shift from reactive firefighting to proactive balance. This presentation shares real-world lessons from software product development—both successes and failures—to explore how we can build a more integrated, adaptive approach to managing risk together.

• Business risks — like shrinking sales, competitor pressure, budget constraints, and inefficient processes—threaten viability.
• Product risks — such as overly ambitious plans, shifting priorities, staffing shortages, and building the wrong thing—disrupt delivery.
• Process risks — like excessive context switching, too much work-in-progress, slow handoffs, and knowledge silos—undermine efficiency.
• Technical risks — ranging from poor design and quality issues to platform complexity and delivery pressure—erode adaptability.

Yet these risks are typically managed haphazardly, as independent concerns, handled by executive, product or technical silos. Usually, the loudest or highest-paid voices determine priorities, while important risks go unaddressed. The result? Compounding problems that stifle agility. We can do better.

Video producer: https://oredev.org/