Agile Development Methods

The information technology always require changes and updation time to time, because new technologies and techniques are coming in the market, that’s why, it is essential for the business organizations and companies to change and upgrade their information technology systems. Similarly, the requirements of the people and customers are also being changed with the passage of time and to fulfil the requirements of the customers companies are looking to change and upgrade their information technology system and environment.

Businesses continually adapt to a changing environment to maintain their market position (Appelbaum, Habashy, Malo, & Shafiq, 2012; Biedenbacha & Soumlderholma, 2008). Change is inevitable considering the current rate of technological advancement and the growth in global competition (Appelbaum et al., 2012; Armenakis & Harris, 2009; By, 2007). Increasing competition and the need for strategic flexibility and globalization is affecting almost every organization today, regardless of size, market, focus, and so on (Jaros, 2010).

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.

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

We live in an environment which changes often. In the business world, what is in demand today for an organization may not be a requirement for tomorrow. Smart managers know that organizations that succeed do so because they adjust to keep up with the changes that are taking place (Harmon, 2007). Change in business comes in many forms and affects companies in every industry. Business today is one of the dominant institutions in society. Businesses are established with the sole purpose to provide a product or service to a customer with the intent to make a

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

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.

Choosing a proper method for software design is completely depended upon the requirements and end products of the company. These requirements and goals might change in the process of development of software depending upon the decisions of stakeholders, developers and system analysts.

There are various agile methodologies. The philosophy of the various agile methodologies are the same like iterative approach in managing a project but they differ in some of the practices they follow in tackling and managing the tasks.

This paper reviews agile software and its strengths and weaknesses.,Likewise, it talks about the four factors that apply in agile software: product, project, process and people ,in addition to some methodologies of agile software such as Scrum, XP.

During this research on agile development methodology, we have taken various Research papers, Magazines, online Journals and news articles into consideration. This research helped us to comprehend that all agile methods follow the four values and 12 principles of the Agile Manifesto. This paper explores the challenges open in agile systems development while adopting it in an organization. Additionally, we also analyzed the solutions to these challenges.

Agile methodology is an approach to project management and agile software methodology is not a one methodology but a set of methodologies which share common characteristics to achieve business goals. Before 1950’s project management have taken place in an informal way for many eras and after an ameliorating of formal project management methodologies began to be defined and swiftly spared through the industry rather than traditional methodologies. The traditional approach of project management identified a set of sequences of steps to be completed such as initiation, planning and design, execution and construction, monitoring and controlling and completion but not all projects will have every stage and some projects can be terminated before they reach completion. When it derived to IT industry in the past few years there’s been

This report is to discuss about the SCRUM (also known as Iterative Development Model), one of the famous software development methodology besides the Waterfall method.

Ever since the Agile Manifesto came into existence in 2001, it has led many agile software development processes to spurt up. Dynamic Systems Development Method (DSDM), Extreme Programming (XP), Feature Driven Development (FDD), SCRUM and Crystal Methodologies are some of the most famous agile software development methodology famous today (Vlaanderen et. al, 20011), (Dingsøyr et. al, 2012). In the recent research done by (Dingsøyr et. al, 2012), it’s been found that XP and scrum are the two most common agile methodologies used currently. In their empirical research (Dingsøyr et. al, 2012) also found that most of the existing studies on agile methodology focus on XP and there are very limited studies done on SCRUM. The purpose of this literature review research is to analyze the existing research available on SCRUM methodology. This literature review will provide a broad overview on various information researchers are providing on agile software development methodology, keeping Scrum agile methodology in the focal point. In addition, this literature review will also address the advantages and disadvantages of SCRUM agile methodology. This research will help the audience to gaze over the recent study over scrum and will help in making the decision whether Scrum is the right agile methodology for their software development project.

This paper discusses about Traditional Software engineering, Agile software development, the Waterfall software development model and also a new concept of Agile software engineering. After a thorough analysis of the paper, I could relate it to topics of Traditional Software Engineering (TSE) which is the process of developing software products. It deals with Cost estimation and budgeting, scheduling, Requirements analysis, Design, Implementation, Testing and Deployment, Measuring products and processes, Quality improvement, Maintenance and so on… Another concept that I could relate to was