deployment, development methods, integration and cybersecurity complexity, and regulatory frameworks. These all elevate the risks and consequences arising from IT project misalignment and ensuing contractual disputes between Suppliers and Customers. Research methodology The following methodology was adopted: • A survey was issued that focused on the sequence of IT Project phases (ie Procurement, Analysis, Design, Build, Testing, Deployment and Production (Support and Maintenance). The survey asked quantitative and qualitative questions concerning key activities in each phase and the extent to which IT Project misalignment occurred in those phases, what that misalignment was caused by and the extent to which it contributed to an ensuing IT Project contract dispute (ie was it a primary or contributory cause?). The survey also raised questions relating to the behaviours observed when an IT Project contract dispute emerges and individuals’ experience of dispute resolution methods used. • Senior industry IT Project stakeholders then responded (including CEO/CIO/PM/SA/Program/QA lead/Sales/Legal/other) from 8 countries (New Zealand, Australia, China, Singapore, United Kingdom, Germany, Italy, United States of America). Over 80% of survey respondents had extensive IT Project experience. • The survey respondents represented a balanced spread of Supplier and/or Customer experience and in key verticals (financial services, utilities, FMCG, telecommunication providers, retail, and government agencies). • Based on this rich data a draft report was prepared and, with a number of survey respondents and additional senior industry stakeholders, further feedback was sought. Research objective The objective of the research was to use the outcomes to review, assess, explore and develop tailored dispute resolution methods that will best assist Customers and Suppliers in improving IT Project success and maintaining Customer-Supplier relationships (the DR Research). DR Research key outcomes These are summarised below: A. When IT Project misalignment most often occurs and its primary causes: • IT Project delivery misalignment and the emergence of a contractual dispute most often occurs in the period after IT Project Contract execution and during the Solution delivery phases. • The qualitative and quantitative survey responses and consultation identified two distinct IT Project phases, and primary causes within those, that lead to IT Project misalignment. 1. Procurement phase: Various Customer and Supplier actions in the Analysis and scoping of transformational Customer Requirements for a proposed Solution were the dominant inadequacy, as distinct from activities in other IT Project phases (Design, Build, Testing, Deployment and Production (Support and Maintenance). In particular these activities include: a. Business case preparation - driven by Budget constraints and expeditious target business outcomes of a Sponsor, often there is a lack of time spent in reaching a full understanding of transformational scope (Current State to Future State), User needs, optimal Solution selection and the Business Objectives. In this context, Supplier bid or sales teams respond. The direction of travel then shifts to ensuring successful project progression of the selected Solution rather than a Solution delivering an optimal outcome based on fully understood business Requirements. b. Internal Requirements scoping - inadequate analysis of User needs and reDesign scope together with deficiencies in internal Customer planning coordination, resourcing and contributory engagement of all relevant stakeholders. This leads to Supplier and Solution selection on this basis, with Suppliers responding to the “factual situation”