How Agile Development Has Improved Quality

Introduction to Agile Methods by Hayes and Andrews gives detailed-oriented information about different aspects of agile methods like why there is a need for new software development processes and pitfalls of traditionally methodologies and how this lead to emergence of agile methods. They describe various existing agile methods but describes only one in great detailed – Extreme Programming(XP). They define Extreme Programming as agile, adaptive software methodology having well defined values - Communication, Simplicity, Feedback, and Courage. Failing in achieving this values will result in failing Extreme Programming. Extreme Programming is used only when you have complete understanding of the business and requirements. Extreme Programming follow a series of iteration to deliver the final project. Initially the story heard from the customer is broken down into smaller stories such that the developers can assign time to develop that stories and then its deliver to the customers for feedback. Coach plays a vital role in Extreme Programming. Afterwards Hayes and Andrews describe how XP differs from traditional methodologies. They also explain the common misconception about Extreme Programming is spread around the world. There are only fewer companies in the world that uses Extreme Programming because people are afraid of changing to new methods.

Thus, Agile came into play. This is a faster and smaller method over traditional. Stakeholders get together with small teams to look at cost, resources and expected time frames. This team figures out the computer verbiage, checks and balances, verification coding, iterations, number limits, scripts, all in the early stages of development.

XP is one of the agile methods which is defined as Extreme Programming, many new developers and designers are tending to follow these methodologies than the age old techniques. But managers who are accustomed to the traditional way of software development are finding it difficult in accepting these new approaches. Furthermore the plan-driven approach also has many underlying advantages such as focusing on the major goals of the project which is named as “major milestone” on the contrary to “micro milestones or inch pebbles”. In the plan-driven approach more planning is emphasized which pressurize the development teams to follow the pre specified documentation even at the minor levels of modification at technology, commercial and personal aspects. The author of the article suggests that there should be at least three milestones in the software development process. Firstly for the progress of the project in order to know the current status of the project. Secondly for the stakeholder’s checkpoint i.e. to check the progress on the development process form the stakeholders point of view whether the commitment given to them is fulfilled or not. The planning spectrum demonstrates the models on straight line where the unplanned hacking is on the left of the spectrum and the inch pebble in on the extreme right.

Agile techniques should be used to solve the current issues faced by the company as agile techniques normally being used by the software industry help the business to act in response under the unpredictable situations faced. In Agile methodologies opportunities are been provided to evaluate whether the project is under the direction all through its development cycle. All this is being accomplished with the help of regular tempo kept in work, and the teams must show a product which is having the desired potential.

Among the various approaches adopted in project management is Agile Methodology, one that is mentioned frequently among experts and considered as one of the key approaches adopted in organizations. As pointed out by Stare (2013), Agile Methodology can be described as a particular way that is embraced in the management of projects and teams in Information and Technology among other fields. There are various practices associated with the Agile Methodology and some of them include the ability to assume simplicity, creation of documentation based on value, enabling rapid feedback to all stakeholders, and embracing change among others practices. Since its emergence in project management, various research studies have been conducted in a bid to explore the possibilities of using the Agile Methodology in other industries that are not specifically meant for software development. Given the fact that corporations are

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].

The cost of changing program doesn’t change over time as extreme programming follows some of the practises like getting feedback from customers, coding and testing frequently and eliminating defects early, and Involving customers in every stage of development

Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. In most Agile methods development cycles are limited by 4 weeks. Teams work in a high tempo, preferring to deliver not a spotless software increment but a workable build which can be shown to the customer and later modified according to the feedback. This helps to avoid spending time developing software with functionality which will be rejected by the

Agile Development is a term coined in 2001 during two-day meeting between seventeen people who gathered at Snowbird Ski Resort in the Wasatch Mountains of Utah(Highsmith, 2001)[3]. The people gathered were the software pioneers trying to establish a common ground and a united stance in worldwide software development community. The outcome was an extraordinary Agile Manifesto for software development. The below table gives an influential value set from The Agile Manifesto of 2001.

The phrase agile refers to a software development methodology which promotes a project environment for adaptation, rapid delivery and client focus, self-organization and team work. Agile software development methodology is a conceptual framework for

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).

Agile software development refers to a group of software development methodologies e.g. Dynamics System Development Model, Crystal Methods and Extreme programming (XP methodology). Agile methods attempt to minimise the risk in software in short time boxes called iterations. Every iteration includes all the tasks necessary to release the mini increment of new functionality: planning, requirements analysis, design coding, testing and documentation. At the end of every iteration the priorities will be evaluated. Agile methods emphasise real time communication, preferably face to face instead of written documents. Agile methods also emphasise working software as the primary measure of progress. Agile methods produce very little documentation compared to other methods. Most Agile teams are located in a bullpen and include all the people necessary to finish the software. (1) (3)

Agile software development is a collection of software development methods where requirements and solutions evolve through collaboration among self-organizing and cross-functional teams. It promotes flexible planning, progressive development,

Key principles described by Extreme Programming (XP) are communication, simplicity, feedback, courage, and quality work (Beck 2000). Extreme programming practices can be followed only when team size is small. This is not suitable process for distributed teams. Project length is general short which is around 2 weeks.

This paper shows a survey of three spry methodologies including Extreme Programming, Agile Modeling, SCRUM, and depicts the contrasts in the middle of them and prescribes when to utilize them.