8.2.1 To V or not to V – that MUST be the Question Knowing When to Apply the Right Approach. Issue 1 (July 2014)

• Record Type: Journal Article
• Authors: Cowper, Doug; Elphick, Jon; Kemp, Duncan; Evans, Rhianne
• Is Part Of: INCOSE International Symposium. Volume 24:Issue 1(2014)
• Page Start: 793
• Page End: 814
• Publication Date: 2014-07
• Subjects: Systems engineering -- Congresses; Systems engineering -- Periodicals; 620.0011
• DOI: 10.1002/j.2334-5837.2014.tb03182.x
• Languages: English
• ISSNs: 2334-5837

Abstract

<abstract abstract-type="main"> <title>Abstract</title> <p>The last 20 years have shown a dramatic expansion in Systems Engineering theory, knowledge, knowhow and practical application. Despite this increase, there is evidence within organisations that there has been a growing gap between the SE required and the SE delivered. The authors of this paper describe the results of a study into the reasons for this gap, based on an on‐line survey which received 85 valid responses.</p> <p>The authors conclude that:</p> <p> <list id="iis203182-list-0001" list-type="bullet"> <list-item> <p>Project professionals are using approaches that are not appropriate to the problems being tackled;</p> </list-item> <list-item> <p>Behaviour is being driven by narrow views of what organisations believe is right, rather than the broader range of practice that they allow;</p> </list-item> <list-item> <p>Project professionals adopt preferred approaches which they apply across more than one type of problem.</p> </list-item> </list> </p> <p>The authors demonstrate that there is truth in the assertion that Systems Engineers apply the same approach, irrespective of the situation. Whilst standard Systems Engineering approaches, for example the V lifecycle, are the right approach in the <italic>complicated</italic> space, it is less appropriate in <italic>simple, complex</italic> or <italic>chaotic</italic> spaces. All too often, projects start with the assumption that we should use standard Systems Engineering approaches that we have used before, rather than ask: 'To V or not to V?'</p> </abstract>