‘Requirements-Uncertainty’: Is it best formulated as a latent, aggregate or profile construct?
研究了经验丰富的信息系统项目经理如何应对需求不确定性的不同维度，提出将需求不确定性表述为轮廓构念而非潜在或聚合构念，以增强其对实践的指导意义。
This paper identifies the strategies that experienced information systems (IS) project managers say they use to cope with requirements-uncertainty (RU) when managing development projects for external clients. It is shown that project managers (PMs) claim to use different strategies for coping with the different dimensions of requirements-uncertainty, as this notion has been formulated in IS literature. Based on this finding, it is proposed that perhaps requirements-uncertainty should be formulated as a profile construct, and not as a latent or aggregate construct, if it is to have pragmatic validity as a guide to action for project managers.