Key points are not available for this paper at this time.
A recent survey with project managers of highly distributed projects at Siemens Program and Systems Engineering (PSE) brought up as main challenges: more severe communication hurdles compared to collocated teams and higher effort to communicate requirements in the team. In this paper, we address requirements tracing options to facilitate risk management with requirements clarification, collaboration, and knowledge management. We propose concepts for enhanced requirements tracing that include the rationale for requirements, related decisions, their history; and stakeholder value propositions. We sketch a cost-benefit model that helps the project manager to understand what tracing approach is worthwhile to address requirements risk in a project. The outcome lays the basis for planning empirical studies at PSE.
Heindl et al. (Tue,) studied this question.