Advantages Of Extreme Programming

Agile processes do not devote much time up front to formal system specifications, but rather relies on continuous communication with the customer throughout the development process. The process accounts for the fact that needs often change or cannot be fully developed early on and is flexible to this. (+)

Agile methodology is a software development lifecycle which designed to produce faster development and high quality results compared with the traditional lifecycle. The Agile method focuses on incremental and iterative development where requirements, specifications, design, implementation, and testing continue throughout the project lifecycle (Nanthaamornphong, Morris, Rouson & Michelsen, 2013). Agile software development methods enable software developer to be more flexible and responsive to the changing environments and customer demands. However, Agile adoption comes with special challenges and fundamental organizational changes are necessary for successful outcome.

Now that I have explained the processes and practices of extreme programming I want to relate some of those practices to explore adopting the XP methods, advantages found, and some failures that can occur while using

Agile is an iterative and incremental (evolutionary) approach to software development which is performed in a highly collaborative manner by self-organizing teams within an effective governance framework, with "just enough" ceremony, that produces high quality solutions, in a cost effective and timely manner which meets the changing needs of its stakeholders [1].

Also, agile software engineering sought to ensure the continued and rapid delivery of changes and new ideas would impress upon the customer that the engineers were able to react to constantly changing situations (Cockburn, 2001). Meanwhile, it was also considered important to allow for constant changes, including changes at the very last minute, just as the product was ready to be unveiled. Finally, it was felt that the process had become almost more important than the outcome, so agile software engineering favoured the production of working software, which it saw as the principal measure of progress (in terms of regular deliveries of beta versions), rather than long-term targets (Eckstein, 2004).

In this paper, Rapid Application Development (RAD) and the Agile Development Method (ADM) are compared and contrasted. The paper begins with a summary of each of the articles referenced on the title page, including the pros (benefits) and cons (risks) of each method. The paper then addresses how the two methods might be applied to my company, Parametric Technology Corporation (PTC), an enterprise software solutions provider headquartered in Needham, MA, with about 6,000 employees in over 70 offices worldwide. Finally, the paper concludes with my views on which of the two methods would be more valuable in a development setting. The authors of the article, “Risks of Rapid Application Development,” open by cautioning that software development includes – or should include – more than the speed at which an application is delivered, identifying maintainability and reusability as equally important characteristics. The purpose of the article is to fill a gap in the literature (at the time of the writing of the article) about the long-term implications of RAD tools on both the software itself and the organizations and developers who use it. The authors emphasize that the choice to use RAD is not just a capability decision, it is also a human resources management decision. In addition to a much faster development lifecycle, RAD tools also include requirements planning, design and modeling, code writing, and testing, with the requirements and design phases accounting for about 30% of

Agile software development is defined as “set of methods that support incremental software development” [1]. Agility means responding to changes quickly and efficiently, flexible production system. Possible changes required in software projects are in requirements, budget, schedule, resources, technology and team. For successful software these changes should be reflected in the product. The term agile software development and the agile golden principles were defined in agile alliance meeting in 2001.

Extreme Programming is one of the popular agile processes (Wells) and is about social changes (Beck and Andres). XP has been proven as one of the successful customer satisfactions since it delivers potential software that can be used, as the customer needs it. It continues to empower developers as it focus on developing excellent programing techniques and communication (Beck and Andres). Extreme programming includes collaborative teams in order to accomplish and solve problems as efficient as possible (Wells). Extreme programming hav five essential ways to improve software projects such: communication skills, simplicity, require feedback, respect and courage (Wells). An XP programmer requires maintaining communication with customers and colleague, and sustaining their design simple and clean (Wells). Programmers are to get feedback by testing the software, and delivering end system product to the customers as early s possible (Wells). Lastly, programmers respect their colleagues as they, together, courageously respond to the changing and evolving technology (Wells).

This essay involves the comparison and contrast of the different methodologies used by programming teams. Among these methodologies are; System development life cycle (SDLC), Extreme programming and Agile methodology. Software development methodologies are the frameworks involved to structure, plan and control the processes used in developing an information system. The system development life cycle (SDLC) is a conceptual model which is involved in most project management and used for large scale projects with relatively large number of developers. A good example of SDCL methodologies includes; waterfall model. The SDCL takes a lot of time to produce complete products but of high quality. Agile methodology is a conceptual framework used also in project management and it is designed for small projects with few developers. Extreme programming on the other hand allow for communication with customers and by doing so it ensures interaction between developers and consumers in order to change as fast as the customers' needs and desires changes. Even though there different methodologies, agile methodologies seem to have a lot of advantages over the Extreme programming and system development life cycle. Since it combines a number of other methodologies to come up with a better way for developer to produce faster and change to as customers desires changes.

During the last few years the adoption of agile methodologies in software development [1], [2], [3] has been increased. The most popular agile methodologies in practice are eXtreme Programming (XP), Scrum Development Process, Crystal Methodologies (CM), Dynamic System Development Method (DSDM), Lean, Kanban, Feature-Driven Development (FDD) [4], [5], [6], [7], [8], [9]. All these methods came into existence to tackle the obstacles in the software project like change in requirements, customer satisfaction, communication with client for good quality product and to support interactions [1], [6], [11]. Agile methodologies are

As Manual tester on other hand, can simply forget to perform some specific tests he may not perform some test at some deployments intentionally.

Agile in its current state, on the other hand, tries to balance speed and efficiency with product quality. Several Agile methods were developed a few years after RAD in order to address volatile environments where needs are not immediately known at the start of a project. These methods also work well in environments where customer needs are constantly changing. Current agile methods are nimble, able to adapt quickly, and able to be modified to suit the environment, the type of project, or development team’s needs. It requires a lot of customer and stakeholder involvement.

There was a need to change our software development process to something that was more transparent, collaborative and iterative. There were few options available that suited our needs however it wasn’t an over night change in methodology. We tried few options like Feature Driven Development methodology and also for Rapid Development methodology for some user experience focused applications. However the neither of those were successfully able to resolve effective work partition and collaboration between teams physically located in different geographical locations. This led us to try some other agile methodologies like Scrum and Extreme Programming. We were successful in resolving a lot of management issues with scrum. Extreme programming

Yet another method is extreme programming (XP). It is also a software development method which improves software quality and responsiveness to changing customer requirement (extreme). This program has proved very successful at many companies. It is successful because it focuses on customer satisfaction. Extreme programming emphasizes teamwork. In this program, managers, customers and developers are all equal partners in a team. Extreme programing improves a software project in different ways which are communication, simplicity, feedback, respect and courage. In this method, programmers constantly communicate with their customers. They keep their design simple and clean. They get feedback by testing their software and deliver the system to the customer as soon as possible and implement changes as suggested. Every team member involvement is essential for the success of the program. With this foundation extreme programmers are able to courageously respond to changing requirement and technology (Extreme Programming).

[1]The Agile software development (ASD) methodologies have been established in various streams like academic, educational and also in professional software development. Understanding of how ASD methodologies are used, the kind of acceptance, successes and failures they have in the mentioned streams would be the main exploration. The findings from the web-based survey of Microsoft employees who involved in development, testing and management have indicated that around one-third of the people use ASD and the SCRUM is the most popular ASD methodology. [2]Agile methods can be mainly used in environments which are unpredictable and helps in succeeding over such environments which are in the reality today.