DOCSLIB.ORG

Implementation Process of Continuous Integration and Continuous Deployment Using Agile Technology

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Implementation Process of Continuous Integration and Continuous Deployment Using Agile Technology AEGAEUM JOURNAL ISSN NO: 0776-3808 IMPLEMENTATION PROCESS OF CONTINUOUS INTEGRATION AND CONTINUOUS DEPLOYMENT USING AGILE TECHNOLOGY Prabhu Thangavelu 1, Research Scholar, HITS University, Chennai, Tamil Nadu, India. Dr. M. Rajeswari 2, Associate Professor, HITS University, Chennai, Tamil Nadu, India. ABSTRACT: The software industry operates based onbreaking down larger projects into smaller and simpler bits and assigning each bit to individual teams that integrate, test, and collaborate the results. For several years, software development has followed the waterfall approach which has been found to be more coherent and much free of bugs. But, in a rapidly changing scenario such as this smartphone era where customers demand new features and bug fixes frequently, the software developers find the previous approaches slower and inadequate to meet the ever- growing demands. Agile methodologies such as continuous integration, automated testing and continuous deployment are relatively new strategies that have found a place of prominence among software developers. These techniques focus on rapidly integrating new changes into the software using iterative methods and achieve frequent delivery of functional parts of a software or an application. Numerous studies have indicated that iterative agile techniques have resulted in faster delivery rates and continuous improvement of the quality of software. But as much as the advantages, agile methodologies are relatively new to the scenario and are still ridden with numerous challenges. One of the major challenges for any developer is the implementation strategy that needs to be used for agile techniques as CI and CD are processes in the pipeline for software delivery and proper implementation will ensure the success rate of such methods. Keywords: CI, CD, Agile, Deployment, Testing, Software development INTRODUCTION: In a rapidly developing software industry, the requirement for adaptive techniques is increasing parallelly. Continuous integration is one such software development technique where the work is integrated continuously daily and tested for integration errors leading to better cohesiveness in teamwork and software development.Agile techniques offer great flexibility and Volume 8, Issue 8, 2020 http://aegaeum.com/ Page No: 1641 AEGAEUM JOURNAL ISSN NO: 0776-3808 adaptability in software development that requires frequent changes based on the customer expectations. These techniques have been found to be greatly successful as the work of team members is continuously integrated and tested to avoid irrelevance and functional pieces of the software or application are regularly deployed as soon as they are ready. Continuous integration and deployment are iterative and people centric approaches and make software development much adaptive and simple in comparison to its predecessor known as the waterfall approach. These agile methodologies have been found to be a great support mechanism in an everchanging software environment (Euro Laukkanen, 2015) and is important for prompt delivery of new features. Agile methodologies are quite relatable and practically applicable in a software industry which has greatly moved towards rapid development of mobile applications which requires frequent updates and security patches on a day to day basis. Agile techniques emphasize on the four core values of interaction over the development process, deployment of working models, rapid responses to changes and encouraging customer collaboration in the development process. Any industry grows on the simple factor of satisfying customer needs. The software industry is no different and needs to adapt continuously. Studies conducted on open source software development have proven that continuous integration greatly influences and improves the product quality and benefits developers greatly (Barbara Russo, 2009). Continuous integration(CI) and Continuous deployment (CD) are mostly perceived as separate processes but both CI and CD are phases in a software delivery process where customers get access to new features and bug fixes at a faster rate. Though agile techniques have been found to be successful, a well-defined implementation process is still under question as these methodologies are iterative and hence arriving at a finish line is not possible. These methods are highly exploratory in nature and hence extensive studies need to be done on the most beneficial methods of implementation strategies. STATEMENT OF THE PROBLEM: Continuous integration and continuous deployment arebased on a set of rules for operation and certain strategies and practices to be followed that help a developer or a team to deliver changes in the code more frequently and also increasing reliability on the code integrity. The implementation process of CI and CD is known as the CI/CD pipeline and is one of the best agile methodologies in practice. The objective of using such methods is based on business Volume 8, Issue 8, 2020 http://aegaeum.com/ Page No: 1642 AEGAEUM JOURNAL ISSN NO: 0776-3808 requirements, Code integrity and quality and security. Technically CI establishes an automated approach to building and testing applications with consistency leading to better collaboration.CD is the continuation of CI and delivers applications to selected environments. CI/CD automation tools follow the necessary procedures that are imperative in deploying the applications. The Study aims at understanding the agile process and the practices that are beneficial to developers in the CI/CD pipeline as continuous delivery is not the only solution for every application used in business. Objectives of the study: • Understand the CI/CD pipeline • Understand various control tools, integration servers and deployment tools • Analyze problems faced by developers while using agile techniques • Discern beneficial strategies for implementation REVIEW OF LITERATURE: Eero Laukkanen (2015) attempted to study the adoption of continuous integration in research and development. Continuous integration is a support mechanism which is important for delivering new features promptly in an everchanging software environment. But studies have revealed that social challenges make adoption of CI in industries exceedingly difficult. The study was conducted in a R&D program inside Ericsson and attempts to understand the stakeholder’s perception on the need for adoption of continuous integration. The author was able to deduce that the product architecture had a considerable impact on the adoption of CI. Training the team for CI was also imperative and needed sufficient learning space and time and most importantly cross site communication was necessary instead of centralizing. Likoebe M. Maruping (2009) attempted to understand the use of agile techniques under various conditions by using the control theory. The author tries to analyze the effectiveness of agile methodology in improving the quality of software projects.Deployment of agile techniques offers immense potential in improving the outcome of a software development project.Extremely limited studies have been conducted on methods to maximize the effectiveness of agile methodology resulting in ambiguity to the project managers. 862 developers were studied based Volume 8, Issue 8, 2020 http://aegaeum.com/ Page No: 1643 AEGAEUM JOURNAL ISSN NO: 0776-3808 on four objectives that influence the project quality.Use of agile methodology proved more useful in occasions where project control was imperative in a changing environment. Barbara Russo (2009) conducted a study on the common factors between open source software development and use of advanced approaches such as agile methodology. The author attempted to understand the how developers benefitted in terms of quality and client satisfaction. The study analyses the strategies that may be used in implementing agile techniques in open source software development for software advancement. Studies such as this will benefit project managers and developers greatly. Yunfang Guo (2019) states that continuous integration is indispensable in a software industry where prompt delivery of new features and bug fixes is imperative. The author builds his research on the findings of Bernardo, da Costa &Kulesza (2018) and attempted to recreate the research conceptually using a adaptive technique of regression discontinuity design and attempted to analyse how many open source projects were successfully able to deliver pull requests (PR) faster by adapting a continuous integration technique. Hilton et al. (2016) conducted a study on 34,544 open source projects and conducted a survey on 442 developers who were known to use continuous integration and deployment techniques in their projects. The author analyzed the effectiveness of the projects based on delivery speed of pull requests and concluded that continuous integration techniques led to faster release and frequently as much as twice in comparison to projects that did not use CI. Also, the acceptance rate of PRs was faster in the median. Vasilescu et al., (2014) argues in his study that continuous integration techniques provide several benefits such as quick delivery of new features and functionalities and at the same time reduces problems that arise in collaborative environment such as incoherence and lack of code integrity. This also improves the stability of the entire software in the mainline. SUGGESTIONS: Extensive study of literature has led to a few suggestions that have been at the core of every successful implementation of agile techniques.
Load more

Recommended publications
  • Rugby - a Process Model for Continuous Software Engineering
    INSTITUT FUR¨ INFORMATIK DER TECHNISCHEN UNIVERSITAT¨ MUNCHEN¨ Forschungs- und Lehreinheit I Angewandte Softwaretechnik Rugby - A Process Model for Continuous Software Engineering Stephan Tobias Krusche Vollstandiger¨ Abdruck der von der Fakultat¨ fur¨ Informatik der Technischen Universitat¨ Munchen¨ zur Erlangung des akademischen Grades eines Doktors der Naturwissenschaften (Dr. rer. nat.) genehmigten Dissertation. Vorsitzender: Univ.-Prof. Dr. Helmut Seidl Prufer¨ der Dissertation: 1. Univ.-Prof. Bernd Brugge,¨ Ph.D. 2. Prof. Dr. Jurgen¨ Borstler,¨ Blekinge Institute of Technology, Karlskrona, Schweden Die Dissertation wurde am 28.01.2016 bei der Technischen Universitat¨ Munchen¨ eingereicht und durch die Fakultat¨ fur¨ Informatik am 29.02.2016 angenommen. Abstract Software is developed in increasingly dynamic environments. Organizations need the capability to deal with uncertainty and to react to unexpected changes in require- ments and technologies. Agile methods already improve the flexibility towards changes and with the emergence of continuous delivery, regular feedback loops have become possible. The abilities to maintain high code quality through reviews, to regularly re- lease software, and to collect and prioritize user feedback, are necessary for con- tinuous software engineering. However, there exists no uniform process model that handles the increasing number of reviews, releases and feedback reports. In this dissertation, we describe Rugby, a process model for continuous software en- gineering that is based on a meta model, which treats development activities as parallel workflows and which allows tailoring, customization and extension. Rugby includes a change model and treats changes as events that activate workflows. It integrates re- view management, release management, and feedback management as workflows. As a consequence, Rugby handles the increasing number of reviews, releases and feedback and at the same time decreases their size and effort.
    [Show full text]
  • Towards Embedded System Agile Development Challenging Verification, Validation and Accreditation
    Towards Embedded System Agile Development Challenging Verification, Validation and Accreditation : Application in a Healthcare Company Clément Duffau, Bartosz Grabiec, Mireille Blay-Fornarino To cite this version: Clément Duffau, Bartosz Grabiec, Mireille Blay-Fornarino. Towards Embedded System Agile Develop- ment Challenging Verification, Validation and Accreditation : Application in a Healthcare Company. ISSRE 2017- IEEE International Symposium on Software Reliability Engineering, Oct 2017, Toulouse, France. pp.1-4. hal-01678815 HAL Id: hal-01678815 https://hal.archives-ouvertes.fr/hal-01678815 Submitted on 9 Jan 2018 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Towards Embedded System Agile Development Challenging Verification, Validation and Accreditation Application in a Healthcare Company Clement´ Duffau Bartosz Grabiec Mireille Blay-Fornarino AXONIC and I3S AXONIC I3S Universite´ Coteˆ d’Azur, CNRS Sophia Antipolis, France Universite´ Coteˆ d’Azur, CNRS Sophia Antipolis, France [email protected] Sophia Antipolis, France [email protected] [email protected] Abstract—When Agile development meets critical embedded to survive. Moreover, with limited human resources, quality systems, verification, validation and accreditation activities are improvement with Agility usage remains to be demonstrated. impacted. Challenges such as tests increase or accreditation The remainder of this paper is organized as follows.
    [Show full text]
  • Devops Point of View an Enterprise Architecture Perspective
    DevOps Point of View An Enterprise Architecture perspective Amsterdam, 2020 Management summary “It is not the strongest of the species that survive, nor the most intelligent, but the one most responsive to change.”1 Setting the scene Goal of this Point of View In the current world of IT and the development of This point of view aims to create awareness around the IT-related products or services, companies from transformation towards the DevOps way of working, to enterprise level to smaller sizes are starting to help gain understanding what DevOps is, why you need it use the DevOps processes and methods as a part and what is needed to implement DevOps. of their day-to-day organization process. The goal is to reduce the time involved in all the An Enterprise Architecture perspective software development phases, to achieve greater Even though it is DevOps from an Enterprise Architecture application stability and faster development service line perspective, this material has been gathered cycles. from our experiences with customers, combined with However not only on the technical side of the knowledge from subject matter experts and theory from organization is DevOps changing the playing within and outside Deloitte. field, also an organizational change that involves merging development and operations teams is Targeted audience required with an hint of cultural changes. And last but not least the skillset of all people It is specifically for the people within Deloitte that want to involved is changing. use this as an accelerator for conversations and proposals & to get in contact with the people who have performed these type of projects.
    [Show full text]
  • White Paper Getting Started with Continuous Integration in Software
    WHITE PAPER GETTING STARTED WITH CONTINUOUS INTEGRATION IN SOFTWARE DEVELOPMENT Amruta Kumbhar, Madhavi Shailaja & Ravi Shankar Anupindi Introduction DevOps culture is gaining rapid momentum in the IT industry as it enables business to adopt agile software delivery methodologies like Continuous Integration (henceforth referred to as CI) & Continuous Delivery (henceforth referred to as CD) .These methodologies enable quicker issue resolution, instant feedback loops, improved software quality and cost saving to meet the ever- increasing demand to deliver better software faster. It would not be wrong to say that CI-CD practices will soon become the de- facto software delivery standards across the industry. Though both these methodologies (CI and CD) This article compiles insights gained from complement each other, CI is the pre-requisite our practical experiences across various CI phase for enabling CD as the latter is built on enablement programs which we have been Gartner says “By 2016, top of the former. The primary goal of CI is associated with. not only to enable build automation through DevOps will evolve Some of these experiences might vary continuous test and quality checks but also to from a niche to a depending on the choice of tools, provide project insights through reports and infrastructure setup, organization policies mainstream strategy dashboards. Since this phase is all about tools, and project requirements. In spite of the employed by 25 it imposes various integration challenges. differences, we hope, this article will act as Having a good knowledge of the tools Percent of global 2000 a helping guide to all those planning for CI involved, their integration aspects and the organizations” setup in their projects.
    [Show full text]
  • Softwareprozesse: Timeboxing & Continuous Delivery
    Softwareprozesse: Timeboxing & Continuous Delivery BENJAMIN PROJDAKOV The Timeboxing Process Model •Voller Titel: The Timeboxing Process Model for Iterative Software Development •Verfasser: • Professor Pankaj Jalote Department of Computer Science and Engineering Indian Institute of Technology Kanpur • Aveejeet Palit, Priya Kurien Infosys Technologies Limited Bangalore Einführung: Wasserfallmodell •Linear •Nicht iterativ •Lange Entwicklungsdauer typisch •Anforderungen: • Müssen vollständig bekannt sein • Änderungen schwierig •Entwicklung in Phasen •Ergebnis: Vollständige Software •Komplexität der Software eher gering Einführung: Iterative Modelle •Linear •Entwicklung: • In Zyklen • Zyklus unterteilt sich in Phasen •Kurze Entwicklungsdauer pro Zyklus •Anforderungen: • Müssen pro Iteration bekannt sein • Änderungen in nächster Iteration möglich •Ergebnis: Funktionierende Software nach jedem Zyklus Timeboxing Modell •Entwicklung: • In Zyklen • Zyklus unterteilt sich in Phasen • Ausführung mit Versatz parallel •Feste Entwicklungsdauer pro Zyklus • Wochen bis Monate •Anforderungen: • Müssen pro Iteration bekannt sein • Änderungen in nächster Iteration •Ergebnis: • Häufige Releases • Funktionierende Software nach jedem Zyklus Timeboxing Modell: Phasen & Teams •Phasen: •Teams: • Anzahl Variabel • Eine Aufgabe pro Team • Gleiche Dauer ideal • Größe abgestimmt auf Dauer Timeboxing Modell: Phasen & Teams •Ungleiche Boxen führen zu ineffizienter Teamauslastung •Lösungen: • “Right-scaling” von Teams • Ressourcenumverteilung •Kann auch durch Verzögerungen
    [Show full text]
  • Continuous Integration (CI) Needs and Wishes for Developers of Proprietary Code
    Continuous Integration (CI) Needs and Wishes for Developers of Proprietary Code Michael Hilton, Nicholas Nelson, Danny Dig Timothy Tunnell, Darko Marinov School of EECS, Oregon State University CS Department, University of Illinois {hiltonm,nelsonni,digd}@oregonstate.edu {tunnell2,marinov}@illinois.edu Abstract—Continuous integration (CI) systems automate the Open-source projects are often considered fundamentally dif- compilation, building, and testing of software. Despite CI being ferent from proprietary-code projects [6]. Differences between one of the most widely used processes in software engineering, open-source and proprietary-code projects include that open- we do not know what motivates developers to use CI, and what barriers and unmet needs they face. Without such knowledge source projects foster more creativity [7], have fewer defects [7], developers make easily avoidable errors, managers reduce the and assign work differently [8]. However, similarities have also productivity of developers by making misinformed decisions, tool been found, including how GitHub is used [9], overall project builders invest in the wrong direction, and researchers miss many complexity [7], and amount of modularity [7]. opportunities for improving the software engineering practice. There are still many gaps in our knowledge about why Given the large fraction of proprietary code development, un- derstanding how proprietary developers are using CI is vital to developers use CI, and what barriers they face, especially for improving it. projects of proprietary code. What motivates developers to use We present the first study of how CI is used in the proprietary CI? What are the barriers that developers face when using development of software. We conduct 16 semi-structured inter- CI? What needs do developers have that are unmet by their views with developers from different industries and development current CI system(s)? Do proprietary developers have the same scale.
    [Show full text]
  • Continuous Integration in Salesforce Development By: Diptiman Prusty 1
    Whitepaper Continuous Integration in Salesforce Development By: Diptiman Prusty 1. Introduction In current SFDC software development scenario, it pays to be quick to market and be able to focus on the business requirements rather than the development process details. DevOps culture for software development has gained rapid momentum in SFDC development industry in the last few years. It involves adopting agile software development methodologies like Continuous Deployment, Continuous Integration (CI) and Continuous Delivery (CD). This enables them to resolve issues quicker, get instant feedback on new products and features, improve the quality of software and ultimately save cost and gain market share. As we shall see below, Salesforce platform is very well suited to use the Continuous Integration and Continuous Delivery methodology to enable organizations to be agile. Page - 2 2. Agile Software Development 3. CI and CD In Salesforce Business enterprises today face several Continuous Integration (CI) and challenges starting from highly competitive Continuous Deployment (CD) are environment, rapidly changing business development practice that requires scenarios and the need to scale up. developers to commit code into a common To overcome the shortcomings of lengthy software source every time they have working code. development cycle, enterprises today have embraced Each commit known as a check-in gets verified by an the AGILE methodology for software development. automated build process. This allows the problems to be identified early in the development process. By integrating regularly, the team can detect errors quickly, Task Board Burndown To In Done and take necessary remedial action. In fact in recent Chart Do Progress years it has come to encompass the whole cycle from Product code check-in till the production deployment.
    [Show full text]
  • Agile Automated Software Testing Into Automotive V-Model Process
    Agile automated software testing into automotive V-Model process: A practical case Xavier Martin Artal Software QA Manager [email protected] es.linkedin.com/pub/xavier-martin/6/a89/723/ Agenda • Introduction • Automotive Trends: Car Connectivity • Car Telematics project Challenges • Use Case Solution: From V-Model to Agile Testing • Results and Conclusions Introduction What is this presentation about? • Expose a practical case of adoption of Agile techniques in automotive testing • Converge Spice automotive V-Model to Agile Spice V-Model Agile • Present Technical Solution adopted: Automation Test Framework • Discuss results and Agile adequacy to Automotive industry Automotive Trends: Vehicle Connectivity Car Telematics • Car Manufacturers start to add 3G/4G capabilities • Connectivity opens new opportunities to develop services for both clients and manufacturers Connectivity Services – Emergency Call – Fleet Management – Car Sharing – Remote Car Diagnostics – Stolen Vehicle Tracking (SVT) – WOTA Update – Dealer Services – User Premium Services Car telematics: eCall • Emergency Call Service for Europe • U.E Council proposes eCall obligatory in European Cars for end 2017 • Automatic call in case of accident or emergency will force car manufacturers to add IVTU to every new car for European Service • Similar regulations for Russia, USA, BRA and PRC Car Telematics Project Challenges What is an iVTU? iVTU = in Vehicle Telematics Unit - Electronic Unit in charge of granting 2G/3G/LTE connectivity to vehicles - Two Main processors architecture:
    [Show full text]
  • Summary of Extreme Programming by Marc Novakouski Description Extreme Programming (Also Known As “XP”) Is a Popular Software
    Summary of Extreme Programming By Marc Novakouski Description Extreme Programming (also known as “XP”) is a popular software development process which grew out of the growing movement towards Agile processes[1]. The basic idea behind Extreme Programming is to strip out virtually all of the elements of the traditional software process to get to streamline development[1]. As a result, an XP project usually results in a software project in which software development is begun immediately, virtually no documentation artifacts are created, other than “user stories” which are written on index cards, and the project proceeds in an iterative fashion in which prototypes are created with the direct input (and sometimes help) of the stakeholders on a daily basis until the desired effect is created[1]. Finally, a key principle of XP is to expect and even “embrace” change, and XP does this by encouraging “refactoring,” or restructuring of the code on the fly on an as-needed basis. Extreme Programming is essentially a conglomeration of a number of specific “Agile” software development practices and concepts[2] in an attempt to remove the non-essential parts of the development process[3]. There are 12 “core” practices that make up XP, which are separated into 4 key areas: Planning, Design, Coding, and Testing[3][4]. Some practices are considered to be “best practices” of the software industry, such as Continuous Integration and Test Driven Development[4]. However, several practices such as Pair Programming and the System Metaphor are more controversial, and are often excluded in practice[5][7]. Extreme Programming is considered to be a development method suitable for only certain types of projects, such as small projects, research projects, and projects dealing with new technology[4].
    [Show full text]
  • Devops Advantages for Testing
    INTEGRATION AND INTEROPERABILITY Labs found that teams using DevOps experience “60 times fewer failures and recover from failures 168 times faster than DevOps Advantages their lower-performing peers. They also deploy 30 times more frequently with 200 times shorter lead times [2].” The choices of tools and frameworks for all of this automation for Testing has grown dramatically in recent years, with options available for almost any operating system, any programming language, open source or commercial, hosted or as-a-service. Active communi- Increasing Quality through ties surround many of these tools, making it easy to find help to start using them and to resolve issues. Continuous Delivery Continuous Integration Building a CD process starts with building a Continuous Integra- Gene Gotimer, Coveros tion (CI) process. In CI developers frequently integrate other de- Thomas Stiehm, Coveros veloper’s code changes, often multiple times a day. The integrated code is committed to source control then automatically built and Abstract. DevOps and continuous delivery can improve software quality and unit tested. Developers get into the rhythm of a rapid “edit-compile- reduce risk by offering opportunities for testing and some non-obvious benefits test” feedback loop. Integration errors are discovered quickly, to the software development cycle. By taking advantage of cloud computing and usually within minutes or hours of the integration being performed, automated deployment, throughput can be improved while increasing the amount while the changes are fresh on the developer’s minds. of testing and ensuring high quality. This article points out some of these oppor- A CI engine, such as Jenkins [3], is often used to schedule tunities and offers suggestions for making the most of them.
    [Show full text]
  • Continuous Integration (CI) Is the Practice, in Software Engineering, of Merging All Developer Working Copies with a Shared Mainline Several Times a Day
    Continuous integration (CI) is the practice, in software engineering, of merging all developer working copies with a shared mainline several times a day. - Wikipedia THE CHALLENGES OF CONTINUOUS INTEGRATION AND APPLICATION SECURITY TESTING Continuous Integration allows companies to generate up to hundreds of builds a day and cope with multiple code changes in a short timeframe. Continuous integration has become more popular following the increase of software development groups adopting the agile methodology. Agile development provides opportunities to assess the direction throughout the development lifecycle. Using regular cadences of work, known as Sprints or iterations, at the end of which teams must present a potentially shippable product increment achieves the ability to assess the product throughout development. Rather than looking at a single planned result, agile allows teams to assess their results every short period of time, usually around two weeks, and if required steer the project in a new direction. In the world of SaaS, agile and continuous Integration/Delivery has and is being adopted quite widely. Development teams are now able to deliver and modify their releases multiple times a day using the Cloud's flexibility and control while at the same time implementing the right techniques to develop quicker and better using agile and continuous integration/delivery. Traditional application security methods are not able to support these quick cycles: 1. Most security testing techniques are dependent on project completion and usually take a long time to carry out which halt the development process and can cause delays to scheduled release dates. 2. Developers are accountable for their code and as such, also accountable for security vulnerabilities found in the code.
    [Show full text]
  • Industry's Experiences with Extreme Programming Practices Dr
    IJRECE VOL. 6 ISSUE 3 ( JULY - SEPTEMBER 2018) ISSN: 2393-9028 (PRINT) | ISSN: 2348-2281 (ONLINE) Industry's Experiences with Extreme Programming Practices Dr. Mohamed Basheer.K.P, Asst. Professor, SS College, Areekode, Malappuram- Dt, Kerala Noushad Rahim M, HSST Dept. of Computer Science DHSE, Kerala Abstract- Agile methodologies are light weight software development II. EXTREME PROGRAMMING PRACTICES processes. Agile processes focus on developing high quality software a. Planning Game. by embracing change in software development. In this paper the Quickly determine the scope of next release. The customer along author discusses the best known Agile methodology called Extreme with the technical people determines the business priorities and Programming (XP), focusing on XP practices and its Software technical estimate is done based on user stories provided by the Industry Experiences. The industry analysis reveals that XP is a customer. As reality over takes the plan, update the plan. This successful software engineering methodology in small projects and will reduce guess work and time wasted on useless features. some of its practices can even be used in big projects. b. Small release. Index Terms- Extreme Programming, XP, Agile Software Put a simple system into production quickly then release new Development, Software Engineering, Pair Programming. versions on a very short cycle. The smaller releases (increments) will reduce development risks, provide frequent feedback and I. INTRODUCTION reduce the overall project slippage. Kent Beck who introduced the concept of Extreme Programming describes XP as a light weight efficient, low risk, flexible, predictable, c. Metaphor. scientific and fun way to develop software[1]. XP contains a set of The system will be described using simple shared stories.
    [Show full text]