RESUMEN

Open source development is often regarded as a chaotic environment where new initiatives' success or failure just happens by chance. However, successful open source communities are applying incubation processes for managing the risks associated with creating new projects. This article analyzes the qualitative and quantitative aspects of the incubation process, focusing on the Apache and Eclipse communities. After performing a quantitative and qualitative comparative analysis of these communities, the authors identified aspects that affect the incubation period's duration and community size. The similarities led them to propose a two-stage model for the incubation process, which might facilitate its applicability to other open source or industrial organizations.

RESUMEN

Requirements engineering must manage the risks arising from project stakeholders. The Outcome-Based Stakeholder Risk Assessment Model (Obsram) provides guidance in stakeholder identification, identification of stakeholder impacts and perceptions, identification of potentially negative responses that pose risks to the project, and assessment and prioritization of those risks. This information provides valuable input to a risk mitigation plan that let you devote more resources and attention to the stakeholders that pose the greatest risk to your project. A case study offers a practical, step-by-step approach to this process. This article is part of a special issue on stakeholders in requirements engineering.