AGILE SYSTEMS

Agile Systems



Agile systems

Introduction

Agile methods are groups of practices that may apply to various types of projects, but rather limited currently in development projects in computer science (software design). Agile methods are intended to more pragmatic than traditional methods. They involve more than the applicant (client) and provide a highly responsive to its requests. They are the real satisfaction of customer needs as a priority under a development contract (Denning, 2012).

Agile methods are based on a structure (development cycle) common (iterative, incremental and adaptive), four common values declined in twelve principles which derive a practical basis, either common or complementary. Agile methods are a particular approach to software development that involves as much as possible to the customer, thereby obtaining a high responsiveness to his requests. There are a number of these methods, among which should be mentioned those of the Agile Alliance, a nonprofit organization created to disseminate it.

Agile methods emphasize face-to-face communication rather than documentation. Most agile teams are located in a single open office, sometimes called "launch pads". The office should include authors, writers and support documentation, design iteration and project managers. Agile methods also emphasize working software that is the first step of progress. Combined with the preference for face to face communication, agile methods are often criticized and treated as "unruly" by the lack of technical documentation (datacom.com.au).

The goal of agile software development is to make the software development process more flexible and thinner than the traditional approach in the models is the case. One would like to focus more on the objectives to be achieved and consider technical and social problems in software development. Two methodologies of Agile system are widely used which are SCRUM and XP. Many companies have adopted one of the two methodologies in their systems. Multiple customers or stakeholders and distributed environment are handled by SCRUM while XP handles tailored needs. Both of the methodologies are best to be used with small development teams.

Case Studies of Agile Methodologies

European Banks

Extreme programming methodology has its component of agile methodology. The main aim of this methodology is to delivery the projects within time and quality improvement. Overall the banking industry of Europe and particularly the BNP Paribas group has taken a new approach for the new software development project through a methodology with the aim of delivering project within limited time frame and quality assurance and improvement. Before this approach was decided on, the banking sector was working via the 'waterfall' approach. The software development projects were developed through this approach traditionally. This 'waterfall' system is basically used for the production of codes. This also included the testing and end-user acceptance where the analysis, design and development of the cycle were conducted when the project would have been completed. Comparative to this, the agile approach is wide. It is also known as an extreme programming where the testing and end-user acceptance continuous throughout the cycle of the development of the project. It is an iterative ...