in Requirements Negotiation with GSS

from any interventions that could reduce their risks. More than half of these overruns and failures in soft-wa fla red the rea qu Fin kinds of complexity that can manifest in any of these ele-ments. They are: 1) Component complexity (number of es he of e-r-Proceedings of the 35th Hawaii International Conference on System Sciences- 2002re development projects can be directly attributed to wed requirements [15, 16], so there is high potential for ucing the risk of software development by improving processes by which requirements are established. One son why software developers struggle to establish re-irements is that the task is fraught with complexity. ding ways to manage that complexity might be an im-and interdependency among acts and information cu needed to create products 2) Coordination complexity (t frequency, timing, intensity, and interdependencies sequencing interactions required to produce products and 3) Dynamic Complexity (the degree to which r quired products, acts, and information cues and the inte dependencies among them change during the task). EasyWinWin: Managing Complexit