Synopsis Of A Presentation On Programming Advancement

“Agile” was first introduced in 2001, by a team of software engineers looking to improve their adaptiveness and responsiveness to ever-changing requirements. Not knowing where to begin, the team began by formulating principles, which they would use to guide their new development process. Which, in turn, lead to the creation of the Agile Manifesto, and thus a new methodology was born.

One of the initial steps in researching a problem is to know exactly what the problem is and compose a problem statement that unambiguously identifies and defines the problem to research. Sekaran (2003) said, “No amount of good research can find solutions to the situation, if the critical issue or the problem to be studied is not clearly pinpointed” (p. 69). The area of research for this paper focuses on software development, in particular, the study of agile software development methodologies and if these methodologies are successful in delivering software on time, within budget, and includes the requested features.

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.

In this paper, we are going to analyze the most widely known method of project management; agile project management. Agile has gained an enormous amount of popularity in the world of software development over the last few years due to benefits like increased business value and faster ROI, improved visibility and lower development costs, greater ability to respond to requested changes and decreased risk in solution delivery. The Agile Method ensures that value is optimized throughout the development process. The use of iterative planning and feedback results in teams that can continuously align a delivered product that reflects the desired needs of a client. It easily adapts to changing requirements throughout the process by measuring and evaluating the status of a project. The measuring and evaluating allows accurate and early visibility into the progress of each project.

Abstract: Agile software development is a conceptual framework for software engineering that promotes development in iterations throughout the life-cycle of the project .Software developed during one unit of time is referred to as an iteration, which may last from one to four week Scrum is part of the Agile movement. It is a lightweight process framework for agile development. The Scrum method is most often used to manage complex software and product development, using iterative and incremental practices. And results have been shown about significantly increase in productivity and reduces time to benefits relative to classic “waterfall” processes. But scrum method also have some problems and to overcome the problems a new approach is proposed

Agile Software Development: The iterative development strategy focuses on incremental delivery of usable software ("What is Agile Software Development?", 2017)

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.

Agile project management lets software project managers and employees alike adapt to changing circumstances, rather than try to impose rigid formal controls, as in traditional linear development methods.

Also in addition to my studies about Agile, I have made efforts to compare the same with another heavy weight methodology called Waterfall. Comparison include the strength and weakness of the two opposing methodologies and the outcome of a controlled empirical study conducted at Carnegie Mellon University in Silicon Valley by Feng Ji and Todd Sedano.

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

In addition to flexibility and responsiveness, Agile project management focuses on continuous planning, execution, and feedback. Agile methods are designed to adapt quickly to changes; whereas more traditional methods focus on planning the future in detail. Agile methodologies are able to more efficiently bring advances to a project (City A.M., 2015). Research shows that agile methodologies are increasingly popular because it helps employees avoid delivering a wasting time completing a project that is later realized to be the complete antithesis of what was truly needed (Pozzebon, 2015). In short, “agile methodologies enable you to do is deliver something quickly but then adapt it and change it at a given point in time based on what you now know and what you 've already implemented” (Sunday Business Post, 2012)). Agile is juxtapose to traditional project management. Traditional project management methodology is focused on the sequential lifecycle of a project, referred to as waterfall. Waterfall projects are common in the construction of infrastructure such as the construction of a bridge, electrical substation or a highway. The waterfall

One of the most prevalent approaches companies utilize today is Agile. The Agile approach was developed to mitigate many of the shortcomings of Waterfall. “The agile development

In the late 1990’s, there are several methodologies which attract public attention.These methodologies underlined importance of collaboration between the development team and business stakeholders; frequent delivery of business value, tight, self-organizing teams; and smart ways to craft, confirm, and deliver code. The term "Agile" was applied to this collection of methodologies in early 2001 when 17 software development practitioners gathered in Snowbird, Utah to discuss their shared ideas and various approaches to software development. This joint collection of values and principles was expressed in the manifesto of agile and the corresponding twelve principle.Software testing is the one most important attribute for software

The way that software is developed has been rapidly evolving over time, going through many iterations, one genre of which is Agile software development. The Agile Manifesto1 was published in 2001, however the ideas behind it have existed and used since the early 1970’s when E. A. Edmonds published a paper that introduced the idea of an adaptive software development process2. Then in the 1990’s there was a rapid evolution of software development processes. This lead to the creation of scrum in 1995, extreme programming in 1996 and feature-driven development in 1997. Though they were devised before the Agile Manifesto was created, they now all fall under Agile software development. Agile software development methods are generally considered much better than previous methods, such as the Waterfall method, though it is still considered to be in its early stages with many issues3.

In conclusion, agile software development is a very exciting and useful approach, although some project suit agile more than others. The collaboration and visibility can provide a much better and rewarding experience for the team to develop software products. Over the last years, many companies dramatically improved their performances