2000 Australian Software Engineering Conference Requirements-Uncertainty: Should It Be a Latent, Aggregate or Profit Construct? Gold Coast, Queensland, Australia April 28-April 30 ISBN: 0-7695-0631-3
In this paper, I try to identify the strategies that experienced IS project managers say they use to cope with requirements uncertainty on development projects for external clients. I show that project managers say they use different strategies for coping with the different dimensions of requirement uncertainty, as this construct has been formulated in the literature. I then argue that requirement uncertainty should be formulated as a profile construct and not as a latent or aggregate construct as at present, if it is to have pragmatic validity as a guide to action for project managers.
Index Terms:
requirements-uncertainty, theories-of-action, contingency-theory, software project management
Citation:
Tony Moynihan, "Requirements-Uncertainty: Should It Be a Latent, Aggregate or Profit Construct?," aswec, pp.181, 2000 Australian Software Engineering Conference, 2000 Usage of this product signifies your acceptance of the Terms of Use. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb