StudentShare
Contact Us
Sign In / Sign Up for FREE
Search
Go to advanced search...
Free

Integration of Agile Practices into Waterfall for Business Advantages - Research Paper Example

Cite this document
Summary
This research paper “Integration of Agile Practices into Waterfall for Business Advantages" examines the real world of software developers and managers which takes into account the real-world practicalities that require a quantitative research design…
Download full paper File format: .doc, available for editing
GRAB THE BEST PAPER91% of users find it useful
Integration of Agile Practices into Waterfall for Business Advantages
Read Text Preview

Extract of sample "Integration of Agile Practices into Waterfall for Business Advantages"

?CHAPTER 3-METHODOLOGY Introduction This chapter explains the procedures that were taken to test the hypothesis of this study “Agile practices can beintegrated into Waterfall yields business advantages.” The selected qualitative research design proceeded in four phases. The first and second phases involved reviewing of relevant literature followed by questionnaire development respectively. The third phase involved gathering a list of survey participants and distribution of the survey by following IRB guidelines. The fourth, which marked the final phase involved analyzing the data findings and then comparing it with existing literature. Rationale for Qualitative Research Design Acknowledging that people are masters of their own lives, research on how programmers and their managers adopt to new policies and procedures can not be done without interviews those impacted by those new policies and procedures. As Marshall and Rossman (1999) Put it, One cannot understand human actions without understanding the meaning that Participants attribute to those actions—their thoughts, feelings, beliefs, values, and assumptive worlds; the researcher, therefore, needs to understand the deeper Perspectives captured through face-to-face interaction. (p. 57) Thus, qualitative research is the best way to understand such personal, individual perspectives. Qualitative research tends to investigate essential and distinctive features of actions and experiences as lived by a person. Groves (2004) explained that qualitative research does not take place in the lab, but happens in the real world. It deals with how people give meaning to their own experience. Furthermore, it aims to interpret the behavior and meanings that people have given to their experience. Kwiatkowska (2013) observed that the goal is to describe and possibly explain events and experiences. The typical language used are the case study, field study and context. The research types include the case study research, ethnographic research and grounded theory. Qualitative research method is used in research with an aim of gathering an in depth understanding information. It investigates the how and why of making of decisions. Therefore, samples that are smaller but focused are often used instead of large samples. According to Groves (2004), qualitative research methods give information on specific studies cases and general conclusions on informed actions. Groves (2004) observed that the qualitative researchers basically are concerned with processes and practices rather than the outcomes. The focus is mainly on the experiences and perceptions of the participants. Qualitative research involves fieldwork typically whereby observation and recording on events are done. The researcher goes to the site, setting and the people physically to observe the subjects naturally and normally. According to Kwiatkowska (2013), the method was seen as appropriate due to its several advantages: 1. It uncovers the experiences of the people 2. It is less expensive because of the focus on small groups 3. It is flexible The assumptions made for this research were: 1. The information gathered will be sufficient to make a general conclusion on how the integration process can be. 2. The available data on integration of waterfall and agile processes were holistically researched since it was difficult to break down the study into small independent factors. 3. The research will contribute a substantial amount of data that can be used by future researcher to ascertain the requirements for integrating agile into traditional processes. However, the limitations of the qualitative research method approach in a research include: 1. Research error is associated with survey research especially where assumptions on a sample are made that are inaccurate. 2. Qualitative research method only collects data on selected group of participants. This data cannot be used in making general assumptions. 3. The method does not allow conveniently for statistical data collection 4. Qualitative research method is prone to rigidity when questionnaires are developed. The survey questionnaire applied and the method of administering at the beginning by a researcher cannot be changed in the data gathering process. 5. The survey research is not also ideal for issues that attract controversies, or cannot be answered precisely by the participants. 6. Possibility of inappropriateness of the questions. This is because of the standardization of the questions to accommodate large populations Phases of the Research The research process was undertaken in four-phase steps. The first phase examined the literature on Waterfall and Agile methods of development that exists. This formed the basis of Chapter two. It showed that the two methods were researched extensively, but little exists if the two methodologies were combined. To fill the gap, the researcher focused on studies that analyzed the constraints and advantages of Waterfall and Agile integration. In the second phase, this researcher developed a survey questionnaire. The survey questions focused on: (a) core business, size, culture and structure (b) characteristics of the participants such as experience and qualification (c) Details on the methodology of the software including the challenges and the process (d) Details on Agile and Waterfall integration including the advantages and constraints (e) The critical factors for success In the third phase, software developers were selected who work for company A, A multinational financial corporation that is based in US. This is because company A has many Agile and Waterfall projects that were ongoing. Furthermore, the participants in the survey reside in Columbus, OH. This site has approximately 150 application projects using Agile and Waterfall methodologies. There were 250 candidates who listed as IT resource, selected from company employee directory. The survey was emailed to the selected participants of company. Before emailing the survey, the participants were asked to provide their experience level in dealing with methodologies of Agile and Waterfall and years of experience. Participation requests and inquiries on individual participants experience were sent in email. The information was used to filter the respondents to get only the ones eligible for participation. Eligibility included at least 2 years of experience working on a project for development where one or all the methodologies of Waterfall and Agile for instance, the Crystal, XP and Scrum were applied. The informed consent form was sent to the participants before sending the survey questionnaire. The participants who signed the consent form were then emailed the survey. The research aimed at securing a broad spectrum of representation across job titles and representations. The respondents who fell within the direct experience of the developers of the software’s were not considered for the research study. The request for participation was sent through email. The goal was to get a minimum sample of 25 developers of software from company A. However, all the people who responded were included in the research study. The necessity enabled solicitation of the initial figure of 250 until the eligible 25 were gotten. The research activity of selecting participants took about 2 months. The qualification for inclusion of a software developer in the study required a participant to have several qualities, including the minimum 2 years experience with both methodology of Agile and Waterfall. This ensured that the selection got participants who were familiar with both methodologies of software development. Participants were selected based on the background and common experience so as not to restrict the results of the survey. The participants included the skilled managers, architectures, programmers; team leads and certifies IT experts. The management and the technicians were given priority in the study. The selection criteria ensured that the participants felt the effect of both methodologies of software development on business and technical issues. The participants who were selected participated in the survey is listed below: 1. Survey_PID_01 2. Survey_PID_02 3. Survey_PID_03 4. Survey_PID_04 5. Survey_PID_05 6. Survey_PID_06 7. Survey_PID_07 8. Survey_PID_08 9. Survey_PID_09 10. Survey_PID_10 11. Survey_PID_11 12. Survey_PID_12 13. Survey_PID_13 14. Survey_PID_14 15. Survey_PID_15 16. Survey_PID_16 17. Survey_PID_17 18. Survey_PID_18 19. Survey_PID_19 20. Survey_PID_20 21. Survey_PID_21 22. Survey_PID_22 23. Survey_PID_23 24. Survey_PID_24 25. Survey_PID_25 26. Survey_PID_26 27. Survey_PID_27 In protection of the confidentiality of the data collected, an informed consent form was provided. Furthermore, the information obtained was not recorded in a manner in which the human subjects can be identified directly or by the linked identifiers to the subjects. The records were also kept under lock and key for their safety. The research records were labeled with specific generated codes by the number of the respondents. The data was stored in the computer, is password protected. The computer holding the information will also have password protection to ensure it is inaccessible by unauthorized persons. There were 27 qualified participants that accepted the participation. The allowance on inclusion of all the people who responded catered for the additional two hence 27 was still within the sample size out of the initial figure of 250. The fourth phase presents the data findings; describing participants' experience in the methodologies and analyzing the factors that help or hinder integration of Agile and Waterfall. The findings will also be compared with the existing literature. Summary Research into the real world of software developers and managers which takes into account the real world practicalities requires a quantitative research design. To test the hypothesis “Agile practices can be integrated into Waterfall yields business advantages”, the research proceeded in four phases. The first phase, literature review, showed that while much has been written on waterfall and agile, little has been written covering the integration of the two. The second phase, survey development, focused on core business, size, culture and structure, characteristics of the participants such as experience and qualification, details on the methodology helped in filtering participants to the ones that met research requirements. The third phase, participant’s selection, involved getting a list of qualified participants from company A. 27 out of 250 participants accepted the participation and were all included in the project. The 27 participant received Survey requests that they needed to confirm. The fourth phase, data analysis, involved analyzed the data findings as well comparing it with the existing literature. Out of the data conclusions and recommendations were derived. The next chapter explains how data analysis, interpretation and strategies were conducted in this research. References Groves, R. M. (2004). Survey methodology. Hoboken, NJ: J. Wiley. Kwiatkowska, Agnieszka. (n.d.). Online Data Collection: The Current State of “Click” Research. Leffingwell, D., & Widrig, D. (2010). Agile software requirements: Lean requirements practices for teams, programs, and the enterprise. Boston, Mass: Addison-Wesley. Larman, C. (2004). Agile and iterative development: A manager's guide. Boston: Addison-Wesley. Read More
Cite this document
  • APA
  • MLA
  • CHICAGO
(“Gile practices can be integrated into Waterfall yields business Thesis”, n.d.)
Retrieved de https://studentshare.org/information-technology/1402069-agile-practices-can-be-integrated-into-traditional
(Gile Practices Can Be Integrated into Waterfall Yields Business Thesis)
https://studentshare.org/information-technology/1402069-agile-practices-can-be-integrated-into-traditional.
“Gile Practices Can Be Integrated into Waterfall Yields Business Thesis”, n.d. https://studentshare.org/information-technology/1402069-agile-practices-can-be-integrated-into-traditional.
  • Cited: 0 times

CHECK THESE SAMPLES OF Integration of Agile Practices into Waterfall for Business Advantages

Agile Software Development

This report gives an overview of agile method of software development.... This report gives an overview of agile method of software development.... It presents a brief technical comparison with the traditional, non-iterative waterfall model, the intent and guiding principles for agile methods, the people involved its advantages and disadvantages, two common agile methodologies and lastly the future of agile.... waterfall In contrast to the traditional non-incremental models such as waterfall, agile does not have distinct phases of capturing requirements, forming architecture and design, development, testing and incorporating feedback as shown in Figure 1....
8 Pages (2000 words) Research Paper

Effecitve Risk Management in Softwatre Development Utilizing Different Methodologies

Reviewing literature to investigate the framework of agile methodologies in risk management 5.... Introduction of the Research Software development business is a risky industry in that software projects are renowned for high rate of unsuccessful.... In different types of software projects, the ability for mitigating risks might be different because a wide range of methodologies contribute to developing software project such as waterfall model, agile methodologies, spiral model, and V model....
5 Pages (1250 words) Dissertation

The Agile Software Development

These are the main components and elements of agile Software Development.... Constant communication and constant interaction is a central feature of agile Software Development approaches and systems (Fowler, 2012).... Stand-up meetings are therefore an essential part of agile software development and promote constant interaction and the holistic development of software (Stray et.... Background The agile Software Development represents a major exit from the traditional method to software engineering....
36 Pages (9000 words) Dissertation

Survey of Agile and Waterfall Integration in Financial Services

The paper "Survey of agile and Waterfall Integration in Financial Services" explains agile technology attributes to be incorporated within the waterfall technology in software development, the advantages of having a hybrid technology made up of agile technology and waterfall technology in the SDLC....
12 Pages (3000 words) Thesis Proposal

Agile Methods and Software Quality

Moreover, a lot of associations have started to understand major reimbursement from the establishment of agile techniques and their trivial development procedures.... This report presents a comprehensive analysis of some of the main aspects of agile development methods.... This research will develop an understanding of agile development methods, their quality practice and significant factors involved in the overall development of systems.... This report “Agile Methods and Software Quality” analyzes agile methodologies which appeared as a response to major shortcomings in the habitual system development methodologies, as well as advantages and disadvantages, guidelines of performance, tactics, and terminology of those methods....
12 Pages (3000 words) Research Paper

Integrating Agile Practices into Waterfall Methodology

From the paper "Integrating agile practices into waterfall Methodology" it is clear that the advancement of technology has seen the evolution of skills and expertise in the field to have advanced the traditional technologies to the more efficient and effective technologies of software development....
12 Pages (3000 words) Coursework

Software Development Life Cycle

This paper asserts that a set of agile practices can be seamlessly integrated into conventional Waterfall methodologies to enable software developers to improve their organizations' ability to meeting customers changing requirements and enjoy important business benefits.... hellip; Of course, the adoption of combined usage of agile and waterfall had its own share of associated challenges and negative effects.... The study found out that most of the respondents' faced and experienced challenges in adopting combined usage of agile and waterfall methodologies....
63 Pages (15750 words) Thesis

Project Management and Software Quality

he level of effectiveness and performance of the project management method is like measuring a complete business process wherein effectiveness, efficiency, and profitability are important factors of performance (Kelsey 2006, p.... The paper includes a review and analysis of different software development models from waterfall to contemporary AGILE approaches....
15 Pages (3750 words) Term Paper
sponsored ads
We use cookies to create the best experience for you. Keep on browsing if you are OK with that, or find out how to manage cookies.
Contact Us