Chapter 3 Research Methodology

Similar documents
10/4/2013. Sharif University of Technology. Session # 3. Contents. Systems Analysis and Design

Review Protocol Agile Software Development

How to manage agile development? Rose Pruyne Jack Reed

Akhil Kumar 1, Bindu Goel 2

CHAPTER 3 : AGILE METHODOLOGIES. 3.3 Various Agile Software development methodologies. 3.4 Advantage and Disadvantage of Agile Methodology

Agile Practitioner: PMI-ACP and ScrumMaster Aligned

Iteration Planning. also called Iteration Kickoff

A Comparison of Issues and Advantages in Agile and Incremental Development between State of the Art and an Industrial Case

AGILE DEVELOPMENT WITH A CAPITAL A

Software Development Methodologies in Industry. By: Ahmad Deeb

Survey on the State of Agile Practices Implementation in Pakistan

Agile in a Safety Critical world

Cisco Unified Communications and Collaboration technology is changing the way we go about the business of the University.

USAGE OF KANBAN METHODOLOGY AT SOFTWARE DEVELOPMENT TEAMS

Requirements Engineering

Agile Development Overview

Becoming Agile: a getting started guide for Agile management in Marketing and their partners in IT, Sales, Customer Service and other business teams.

Chapter 5: Discussion & Conclusion

The Agile approach Extreme Programming (XP) Implementing XP into a software project Introducing HCI design into agile software development Summary

Value, Flow, Quality BCS PRACTITIONER CERTIFICATE IN AGILE SYLLABUS

AGILE & SCRUM. Revised 9/29/2015

Agile Testing and Extreme Programming

Total Credits: 30 credits are required for master s program graduates and 51 credits for undergraduate program.

Generalizing Agile Software Development Life Cycle

Agile Development for Application Security Managers

LEAN AGILE POCKET GUIDE

Comparing Agile Software Processes Based on the Software Development Project Requirements

Agile and Secure: OWASP AppSec Seattle Oct The OWASP Foundation

Agile Software Development

Procedia Computer Science

TRADITIONAL VS MODERN SOFTWARE ENGINEERING MODELS: A REVIEW

Agile Project Management and Agile Practices Training; with a Scrum Project that you will do.

Testing in an Agile Environment

Prepared by: Your Name (metric card number)

SCRUM BODY OF KNOWLEDGE (SBOK Guide)

Contribution of Agile Software Development Methods to Business-IT Alignment in Non-profit Organizations

STUDENT THESIS PROPOSAL GUIDELINES

Agile Processes and Methodologies: A Conceptual Study

AGILE SOFTWARE DEVELOPMENT A TECHNIQUE

Continuous User Experience Development

Qualitative methods for effectiveness evaluation: When numbers are not enough

How To Understand The Tools Your Organization Uses To Manage An Agile Process

Agile Methods in Software Development (SE 470) Course Details

WE ARE FOCUSED ON HELPING OUR CLIENTS WORK SMARTER AND MORE EFFICIENTLY SO THAT TOGETHER, WE CAN EMPOWER PEOPLE TO DELIVER GREAT RESULTS.

Role of the Business Analyst in an Agile Project

Gothenburg 2015 Jan Marek com CA Technologies Introducing Agile development methodologies to Session S601 mainframe development teams

Agile and Secure: Can We Be Both?

The Role of CM in Agile Development of Safety-Critical Software

User and Client Satisfaction in Agile Development

Becoming a Business Analyst

How To Plan A Project

3 Terms and definitions 3.5 client organization whose management system is being audited for certification purposes

Becoming Agile: a getting started guide for Agile project management in Marketing, Customer Service, HR and other business teams.

Department of Industrial Engineering. Sharif University of Technology

Strategy. Agility. Delivery.

Software processes that are:

Comparative Analysis of Agile Software Development Methodologies-A Review

Determining requirements

Future of CMM and Quality Improvement. Roy Ko Hong Kong Productivity Council

REQUIREMENTS FOR THE MASTER THESIS IN INNOVATION AND TECHNOLOGY MANAGEMENT PROGRAM

Agile In a Nutshell. Note - all images removed to fit 2MB limit Actual presentation has much more content. Jonathan Rasmusson

Getting Business Value from Agile

IT Professional Standards. Information Security Discipline. Sub-discipline 605 Information Security Testing and Information Assurance Methodologies

CLOUD MIGRATION STRATEGIES

A Quantitative Study on Critical Success Factors in Agile Software Development Projects; Case Study IT Company

WHITE PAPER. Leveraging a LEAN model of catalogbased performance testing for quality, efficiency and cost effectiveness


Software Development Life Cycle at SSPL. An Summary of Methodologies We Offer

Planning and conducting focus group discussions in marketing research

Measuring ROI of Agile Transformation

Software Development Life Cycle (SDLC)

Scrum on Offshore Development Case Study

AGILE SOFTWARE DEVELOPMENT. BY Sysop Technology Aurangabad

An Agile Methodology Based Model for Change- Oriented Software Engineering

INTRODUCTION TO TECHXB SERVICES

CHAPTER III RESEARCH METHODS

FINAL WORKSHOP REPORT. IU21KT stakeholders, European Commission, Study Team

Agile Methods. Introduction to. AAddison-Wesley. Sondra Ashmore, Ph.D. Kristin Runyan. Capetown Sydney Tokyo Singapore Mexico City

A SYSTEMATIC LITERATURE REVIEW ON AGILE PROJECT MANAGEMENT

Overview TECHIS Carry out security testing activities

Contents. -Testing as a Services - TaaS 4. -Staffing Strategies 4. -Testing as a Managed Services - TaaMS 5. -Services 6.

Multi-Dimensional Success Factors of Agile Software Development Projects

Higher National Unit specification. General information. Software Development: Analysis and Design (SCQF level 7) Unit code: HA4C 34.

Imad Alsadeq, Qatar, May 2013 OPM3, MSP, PMP, PMOC, PMI-RMP, MCP

How To Understand And Understand The Software Development Process In Korea

Lean QA: The Agile Way. Chris Lawson, Quality Manager

Transcription:

Chapter 3 Research Methodology Over the last decade, there has been a constant increase in the number of software engineering researchers exploring a faster and efficient way of developing mobile applications. For the development of mobile applications using Agile practices, several important objectives were considered and this chapter provides the aims and objectives of this research. It also presents the flowchart of research methodology used, the steps involved in the process of developing research questionnaire and describes the development process of the proposed AgileMAD model, including, procedures used for literature review, questionnaire design, data collection and its analysis. 3.1 Research Objectives The research gaps have been identified based on the literature reviews of the individual studies. Following research objective(s) were outlined that commences with understanding of mobile application process in detail and also includes various mobile application characteristics, issues and challenges, and best practices adopted by mobile development community for a successful mobile application development process. a. To study the mobile application development process using Agile software development methodologies, such as XP, Scrum, Lean, Kanban, AUP, AM, DSDM, FDD and Crystal. Each of these Agile approaches is focused on different aspect and comparing these methodologies is imperative. b. To conduct a technical survey for gaining a better understanding of prevalent development practices for mobile applications thereby identifying the problems and challenges faced by the mobile professionals related to application development. c. To investigate and implement a robust approach for each phase of mobile software engineering process using various Agile methodologies; identifying various challenges faced by mobile developers and best practices followed to build and deliver a successful mobile app. d. To identify the best fitting Agile approach and integrating specific Agile practices, to meet the needs of volatile mobile projects and to assist mobile developers and managers during the mobile application development process.

e. To propose a flexible and extensible process model capable of modelling and selecting suitable agile techniques for mobile application development projects. This can further be tailored and implemented by mobile industries to their best convenience. f. To evaluate the proposed model from Expert/Academic Researcher(s) and to validate the proposed model by developing and empirically testing a mobile application on the latest mobile phone in real organization to actually appreciate its result. 3.2 Research and Process Figure 4 presents the flowchart of research methodology and the proposed model development process used in this study: Literature Review Questionnaire for Survey Unstructured Interview of Experts Data Collection and Analysis of the Proposed AgileMAD Model Coneptual Validation of the Proposed AgileMAD Model Finalization of the Proposed AgileMAD model for MAD using Agile Emprical Evaluation of the Proposed AgileMAD Model Figure 4: Flowchart of Research Methodology and proposed model development process 3.3 Proposed Model Process This section describes the development process of the proposed AgileMAD model, which includes, procedures used for literature review, questionnaire design, data collection and its analysis.

Criteria for Literature Review Before proposing a new model for the development of mobile applications, a systematic investigation of the existing literature was performed. The study instigated and focused on the development of Agile approach for Mobile Application (MAD) for which, the literature review of the subject along with the technical review of the people working in this area was conducted. Literature review emphasized mainly on the mobile application development, Agile software development, existing mobile software development model using Agile approach and other software development products using Agile methodologies (or its combinations). Whereas, for the technical interview, mobile application development community, including top level management, developers and Agile experts were selected and their views, opinion and comments was collected and processed therein (Figure 5). The standard sources used for literature search included online journals and published literature. Adopting an Agile approach for MAD Literature Review Technical Interview Mobile Application Agile Software Mobile Application Community Agile Experts Figure 5: Adopting an Agile approach for MAD Survey and Interview Based on the objectives of the research work (as mentioned in section 3.1), the research methodology utilized in the current study comprised of an online survey that consisted of questions covering the entire mobile application development lifecycle. Since in order to build a great mobile application, it is critical to understand the following and the questionnaire for the

online survey was thus drafted in consultation with the experts in the area of mobile application development and Agile software development: key features that define good mobile applications including- different types, categories and the unique characteristics of these apps mobile application development process issues and challenges faced while developing a mobile app mobile software development best practices which expose the mobile phones from potential threats and attacks reasons of adopting any particular software development methodology in the development of mobile applications, and concerns or barriers regarding using a particular approach In general, Agile principles and practices are considered to be most suitable for mobile application development because mostly, the mobile projects are short-time and require flexibility as they usually have frequent change requests. Based on the above mentioned objectives, the questionnaire for the online survey was drafted in consultation with the experts in the area of mobile application development. The main aim for conducting the online research survey study was to contribute towards a greater understanding of the mobile application development process and to determine suitable Agile software development methods currently being practiced by mobile companies for the development of mobile applications. The complete survey is listed in Appendix C. Alreck and Settle (1995) identified three primary techniques to collect data for questionnaire based survey studies that include personal interviews, telephonic interviews and mail data collection. Although, presently the most popular approach of data collection is to conduct web based surveys (Nardi et al., 2003). The proposed research study presents several motivations for opting online research data collection procedure. First, web based survey enables the data or participants responses to be stored in an electronic form and provides instant and direct access to the database. This further helps to observe study and maintain daily track of the received responses from the participant's. Second, web based survey eradicates the human errors and costs

related to offline surveys. Also, web based data collection prevails certain limitations of mail or paper surveys in terms of time and budget. Third, direct mail data collection shows a low response rate in contrast to web based surveys that show an enhancement in the response rates. The online survey used in the current study was descriptive in nature providing an eloquent analysis. It is noteworthy that descriptive surveys do not explicate or illustrate fundamental relation between variables although they concentrate on elucidating what percentage of a sample has a certain view or how often certain events take place and are associated with each other (Oppenheim et al., 1996). The survey having extensive questionnaire was designed based on the available literature related to mobile app development process and also after evaluating several online surveys conducted in past by various academic and commercial organizations researching on mobile application development. The design of the questionnaire was evaluated and validated by several experts from mobile development community with familiarity or experience in Agile software development before it was handed over to the participants. In selecting the survey respondents, a purposive sampling was used. Purposive sampling involves selecting a unique sample purposely due to its particular feature that is important for the research work (Nardi, 2003). In this study, the industrial participants were those known to have actual mobile application development experience, having in-depth familiarity with Agile software development procedures or the one s interested in exploring it, and those involved in the ongoing research on mobile application development using Agile software development methods. Data Collection, Analysis and Findings

The respondents were invited to participate in the survey via mobile application development forums which covered multiple mobile app platforms development aspects. More than 130 responses were received during the data collection period and the participation in the survey was entirely voluntary. The data was analysed using SPSS Statistics, versions 16.0. The results of the analysis are given in Appendix D. Each response was studied individually, and then detailed analysis was performed on all the responses collectively. The validity of the study and findings was assessed by relevant experts in areas. The results of the survey were utilized as a starting point to identify specific requirements in the area of mobile software engineering for new and revolutionary business practices. In addition, the specific demand of using Agile approach in the area of mobile software engineering was also identified. Figure 6: Research findings of current study Mobile Application Characteristics Most appropriate Agile approach for MAD An explanation on failed mobile projects using Agile Research Findings Issues and Challenges of MAD Best Practices of MAD The Proposed AgileMAD Model for Mobile Application using Agile Practices Suitability of Agile Methods for Mobile App Mobile Software Process Based on the literature review and technical interviews conducted from mobile development community and Agile experts respectively with mobile development experience, various important research findings were established and reported which led to the development of the proposed AgileMAD model as shown in the Figure 6.

Validation of the Proposed Model The analysis of the research findings resulted in proposing an AgileMAD model for the development of mobile applications by integrating specific Agile principles and practices. Study Findings The Proposed AgileMAD Model for MAD Comparing AgileMAD with existing proposed model for MAD AgileMAD Evaluation (Research Experts) AgileMAD Implementation (Case Study) Figure 7: The Proposed AgileMAD Model for MAD Figure 7 depicts the methodology adopted to verify and validate the proposed model and to prove its obligation and exigency. The proposed model was evaluated, verified and validated after performing following actions: a. Comparison with existing Models: Firstly, the proposed model was compared with existing models as proposed by various academicians and researchers for the development of mobile applications using various Agile methodologies (in combination with non Agile techniques). This comparison helped in justifying the necessity of AgileMAD model as a result of this study. b. Evaluation of proposed model: Secondly, the proposed AgileMAD model for the development of mobile applications using various Agile approaches was theoretically evaluated and appraised by academicians, mobile development community members and various professionals in the area. The comments, feedback and observations received was qualitatively analyzed and ideographically summarized. The final AgileMAD model was proposed in the light of the suggestions and recommendations received from respective experts in the area. c. Implementation and validation of the proposed model: Finally, the proposed AgileMAD model after being theoretically evaluated from academicians and industrial experts was empirically tested by implementing and performing case studies in actual mobile development setting in two mobile companies for the final verification and validation.