2011
DOI: 10.1016/j.respol.2010.10.011
|View full text |Cite
|
Sign up to set email alerts
|

Project risk management and design flexibility: Analysing a case and conditions of complementarity

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

1
83
0
2

Year Published

2011
2011
2023
2023

Publication Types

Select...
7
1
1

Relationship

0
9

Authors

Journals

citations
Cited by 109 publications
(97 citation statements)
references
References 48 publications
1
83
0
2
Order By: Relevance
“…Exclusion does not erase conflict, however. If the excluded parties are powerful and influential, they may try to sabotage the development process or lobby for changes that get increasingly costly and risky to implement as development unfolds (Morris 1987, Miller and Lessard 2001, Pitsis et al 2003, Gil and Tether 2011. Hence an enduring goal in various literatures has been to search for organizational forms amenable to design change and concomitant trade-offs between flexibility and efficiency (cf.…”
Section: Resultsmentioning
confidence: 99%
See 1 more Smart Citation
“…Exclusion does not erase conflict, however. If the excluded parties are powerful and influential, they may try to sabotage the development process or lobby for changes that get increasingly costly and risky to implement as development unfolds (Morris 1987, Miller and Lessard 2001, Pitsis et al 2003, Gil and Tether 2011. Hence an enduring goal in various literatures has been to search for organizational forms amenable to design change and concomitant trade-offs between flexibility and efficiency (cf.…”
Section: Resultsmentioning
confidence: 99%
“…As a result, infrastructure projects frequently run late, overrun budgets, and deliver outputs that leave many user groups and communities discontent (Morris 1994, Miller and Lessard 2001, Pitsis et al 2003, Esty, 2004, Gil and Tether 2011.…”
Section: Introductionmentioning
confidence: 99%
“…In practice, in large manufacturing environments with simultaneous design and development of several product lines, a 'single-capture process' approach to requirements is infeasible. One of the impractical assumptions that is associated with adopting a single-capture requirements process is that it is considered a relatively easy task to assign 'content ownership' of any requirement (Gil and Tether, 2011). Identifying content owners for each requirement is increasingly difficult where a physical component might be controlled through software located in a completely different section of the architecture.…”
Section: Organizational and Business Challenges In Creating Complex Pmentioning
confidence: 99%
“…Adding flexibility to the design structure also attenuates conflict because it leaves options open and thus lowers future adaptation costs (Gil, 2007;Gil, Biesek, & Freeman, 2015;Gil & Tether, 2011). But to 'future proof' large integral designs against an array of foreseeable claims invariably demands investment in costly safeguards, e.g., deeper foundations, redundant equipment, and may sacrifice operational performance.…”
Section: The Capability To Develop a Technical Designmentioning
confidence: 99%