Paper Info
Title
Requirements-Uncertainty: Should It Be a Latent, Aggregate or Profit Construct?
Abstract
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.
Year
DOI
Venue
2000
10.1109/ASWEC.2000.844575
Australian Software Engineering Conference
Keywords
Field
DocType
different dimension,different strategy,project manager,profit construct,requirements uncertainty,development project,pragmatic validity,external client,requirement uncertainty,contingency management,prototypes,software project management,contingency theory,uncertainty,financial management,software engineering,systems analysis,management information systems,computer applications,project management,profitability,system testing
Management information systems,Systems engineering,Computer science,System testing,Systems analysis,Software project management,Contingency theory,Computer Applications,Financial management,Project management
Conference
ISBN
Citations 
PageRank 
0-7695-0631-3
1
0.36
References 
Authors
5
1
Name
Order
Citations
PageRank
Tony Moynihan110.36