Abstract
The management of software project development requires a dynamic and reactive environment to meet shorter time-to-market demands to address competition efficently in the software industry. This scenario requires the use of effective and robust methodologieswhere opportunities are not lost due to delays and failures in timely software project deliveries.The Agile Manifesto in 2001 which introduced 4 values and 12 principles was designed to develop and manage software projects in a more suitable and effective way to improvethe success rates of software projects. But, increase in overall success rates are still not significant with failure rates remaining plauteaued at about 30% over the last 10 years. Hybrids methodologies seem to have worked better as agile hybrid management methodshave shown more promise when compared to pure agile methods with an overall success rate increase of 16%. There is evidence too that by combining agile methodologies with traditional methodologies, there would be a further increase in success rates. Whilst many hybrid methodologies have been suggested and researched, the gaps in the literature review reveal there is a lack of hybrid models that have been empirically developed and studied as second order components. To build a robust hybrid model, it is important to gather the relevant information and careful consuideration must be given to the design of the questionnaireto fit second order components and models must incorporate and provide for the use repeatable ways to test models once the data is collected.This paper presents a review of the current gaps in hybrid methodologies and proposes a questionnaire design that supports the research methodology and empirical study to be undertaken with second order components (Constructs).Further it looks at the design approach in questionnaires which incorporates the use of repeatable constructs and the measures used and emphasizes this as an important ingredient for developing and testing hybrid models in research studies.
Highlights
Software development activities are managed in dynamic enviroments(Jabar et al, 2014; Schelling & Pierling, 2015; Gheni et al, 2016)that require reactive approaches (Yang et al, 2017; Sidi et al, 2017; Hussain et al,. 2016)to meet shorter time-to-market demands(Spalek, 2016) and hybrid architectured methodologies have provided opportunities as software project success rate have increased by 16% (Papadakis & Tsironis, 2018)
A hybrid software project management methodology is defined as a combination of traditional and agile software development methodologies and philosophies to create a collective interaction of combination patterns and tailoring strategies (Kuhrmann et al, 2018a; Papadakis & Tsironis, 2018; Hussain et al, 2016)
A value of 1 for the hybrid component indicates that the items in traditional and agile methodologies are fully represented and provides a clear and accurate repeatition in the inclusion of the test and fits the model well
Summary
Project management as a discipline that is not categorized as an exact science and the primary constructs in a theory are required to be well defined (Gregor, 2006) and provide a clear context in the manner it is used (Eri et al.,2012; Niknazar & Bourgault, 2017) and how it is queried (Saad et al, 2014; 2016; Alwan et al, 2016; 2017). 2016)to meet shorter time-to-market demands(Spalek, 2016) and hybrid architectured methodologies have provided opportunities as software project success rate have increased by 16% (Papadakis & Tsironis, 2018). The definition used for failure in the CHAOS report was done on failed projects which typically include projects completed but with a very poor quality both in the product and the processes used (Magne Jørgensen, 2014). Studies in this area would require an initial and independent look at the traditional and agile software project management methodology characteristics and an eventual review of the combined characteristics through models that support the various concepts and theories. Careful consideration is necessary for the design of questionnaires (Roopa S, 2012) which should include the various characteristics as constructs and indicators which use measures and provide for repeatable constructs to study the proposed model in terms of its validity and fit
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callMore From: Turkish Journal of Computer and Mathematics Education (TURCOMAT)
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
