Why Agile Can Be A Popular Software Development Framework
Mon 12 Jan 2015 00:08
Software products penetrate almost every aspect of human existence today. They manifest themselves in a multitude of manner, and remain omnipresent in a host of devices ranging from washing machines and smart phones to automobiles and computers. Owing to a consistent usage of different types of digital devices by people across the world, software applications and utilities have to evolve as and when consumer requirements change and "strive" to fulfil the new set of requirements demanded by end users. It is, therefore, essential to develop newer versions of existing software products more frequently, in the shortest time possible, and in a manner such that end users do not face any problems while using the products in the upcoming months. Stiff market competitions and an ever-increasing consumer "appetite" for feature-rich products have created a special need to implement a reliable and sustainable product development methodology, or a framework, which can aid in developing sophisticated software products in a relatively short time. Moreover, the methodology should also help in reducing the developmental overheads so investment returns can be increased. As on today, a reliable project development methodology is very much required to fulfil the business goals on a consistent basis, and earn large profits from the products manufactured by IT companies.
Over the decades, IT stalwarts have introduced many software development frameworks and project management methodologies. While many of these methodologies have proved to be useless and non-productive, a large number of them have been, in fact, successful in delivering the desired results â€“ with varying levels of acceptance. With the passage of time, two software development frameworks have managed to dominate the field of software development. The frameworks are:
It is a traditional software development framework typically featuring "staged" development processes which have to be "carried out" one after the other. A unique aspect about this framework is that product development starts from the "topmost" stage and "flows" towards the "bottommost" stage. Once started, the product development cycle cannot reverse itself - it is unidirectional in nature. The framework is widely used, and is very popular amongst software development companies, primarily because the framework has "been around" for a long time and used by a large number of software developers and IT firms. It is easy to understand and use. Therefore, it is also used for teaching the software development process to engineering students. Even though it is a much sought after development framework, a large number of individuals and companies traditionally using Waterfall methods for developing their software products are now finding it increasingly difficult to meet the changing global software trends, and developing state-of-the-art applications and utilities, which are so much in vogue today.
A comparatively new "entrant" Agile has managed to find a special niche for itself in the IT development field over the years. The Agile framework was originally envisioned, and developed, to overcome the defects of traditional software project management methodologies and frameworks, which had failed to evolve "in the desired direction", could not adapt themselves to the changing market trends, and offer reduced turnaround times. There are many reasons why "lightweight" Agile frameworks have become popular development platforms:
- They support product development through "short bursts" of programming/development activity, generally lasting from two weeks up to one month. It is much easier to develop, test, and document smaller "pieces" of code, features, and functionality rather than entire projects. Individually developed features are later integrated to form the "complete" product. The frameworks primarily focus upon rapid delivery of "shippable" products and business value.
- The client is actively involved with the team and the development process. Each feature is checked and "cleared" by the stakeholders before it is accepted as "Done". This leads to increased customer satisfaction and enhanced user experience.
- Potential pitfalls are identified well in advance, at a micro level, so it is much easier to control regression and reduce technical debt. Agile software projects generally help to earn good profit margins.
- Agile frameworks support error detection and error correction processes. Technical errors are discovered early during the product development process, and dealt with effectively.
- The frameworks provides an opportunity to carry out "retrospective" thinking, reflect in terms of where the project is heading, and what "more" could be done to improve the product development process.
Agile and the scope of software development
Individuals associated with the software industry generally prefer using the term "software development" to describe their particular line of work. The words are indiscriminately used to describe a host of development related activities, including testing, documentation, debugging, deployment, and maintenance of software applications. It is normal to explain oneâ€™s profession as "software development" while the individual may be working as a VBScript or Java web developer, an application programmer, an iOS or Android mobile apps creator, or even developing specialised scripts for WordPress themes.
One of the commonest doubt prevailing amongst most individuals new to the Agile process is whether Agile is "applicable" to their particular field of work. And if so, how ? In what manner? How can they possibly benefit through Agile ? The questions are many. First of all, it is important to know where Agile is applicable, and whether it "covers" your particular field of work. Please read to know more about Agile "applicability". The list provides a rough idea regarding the scope of Agile software development.
- Clients and stakeholders engagement
- Transparency and collaboration
- Quick and predictable delivery
- Predictable costs and work schedule
- Support for "change"
- Focusing upon the business value
Agile emphasises upon client engagement. The stakeholders "own" the project and sponsor it. Their objective is to develop successful software projects, and generate higher sources of revenue out of them. In practice, the client remains conversant with the current market trends, and possesses a fair idea as to "what" is likely to score in the market in terms of a feature rich application or utility that can satisfy the end user requirements. When the client is closely associated with the day-to-day development activity, he or she can decide whether the productivity offered by the development team can satisfy user related requirements, and how much of business value the product features possess. Client participation leads to meaningful and successful project development and completion.
Waterfall does not encourage or support client participation. The project is developed, and subsequently presented to the client after it is totally completed. Since the client does not participate in the development process, Waterfall projects may fail to offer the exact features so desired, and, in addition, do not "guarantee" any business value for the project. There is a certain risk involved regarding the product's saleability.
The Agile framework makes it possible to increase the transparency levels while working, and facilitates the actual product development process by increasing the collaboration amongst team members. Information pertaining to the entire project is shared equally with all team members, and each decision undertaken by the senior team members - the product owner and the scrum master - is freely discussed. The seniors "act" as mentors, and many a times employ a servant-leader role to increase team participation. The team members have the authority to accept or reject the tasks taken up for development. Moreover, the developers have the right to allocate or distribute development tasks amongst themselves. Seniors do not allocate work to the development team members. All these factors create a healthy working environment. A conductive Agile work-related atmosphere leads to meaningful development and timely completion of product features.
The Waterfall framework primarily concentrates upon delegation of authority and direct allocation of work. Unlike Agile, the development process is pre-decided, and in many cases, even decided as to which resource should be used for developing a particular product feature. Waterfall is rigid as far as sharing of information is concerned. The project related documentation is created at the projectâ€™s onset, and apart from technical information, nothing else is generally shared with the team. The seniors have the final â€œsayâ€ and junior team members cannot argue with any of the decisions undertaken by the seniors.
Apart from the actual development activity, Agile supports several events and activities which constitute the actual Agile process. Each activity is time-boxed and has to be completed within a stipulated time. It is one of the most important framework features. Quick and sustained delivery of shippable products through periodic product incremental cycles known as â€œsprintsâ€ comprise the main heart of all Agile frameworks. The deadlines are stringently adhered to and rarely compromised upon.
One of the biggest drawbacks of Waterfall is that projects, in many instances, extend well beyond their stipulated deadlines, and rarely get completed in time. It is an inherent drawback which actually inspired the "birth" of Agile and Lean frameworks. Traditional development methods are rigid, and it is very difficult to control the rate at which productivity is offered by the team. That is not the case with Agile. Each Agile sprint is dynamic, and "monitored" on a daily basis through the daily scrum meetings so it can be "made" effective. Agile concentrates upon quick and timely delivery of product features and functionality through daily development activity known as "daily sprints".
It becomes possible to predict the amount of work done, or productivity offered, by time boxing the daily sprint iterations. The development carried out can be frequently and easily monitored since each â€œdaily sprintâ€ has to result into something â€œsignificantâ€ with regards the development of product features, and the same has to be exhibited to the product owner and the stakeholders in special Agile events known as the â€œsprint reviewâ€ and â€œsprint retrospectiveâ€ meetings. The â€œvelocityâ€, or the rate at which actual development is carried out, is used for estimation purposes i.e. the total number of tasks developed by the team during a particular sprint provides an idea about how much work was carried within a specified time. The estimation makes it possible to predict how much time and financial resources will be required to complete the project. A reliable project release date can be subsequently stated.
It is very difficult to estimate how much time a Waterfall project will need to complete. Deadlines are generally â€œset upâ€ based upon predictions and project related experience, rather than on actual project dynamics and production pattern. It is one of the primary reasons why Waterfall fails to deliver time bound projects.
Agile is based upon "inspect" and "adapt" principles. The Agile framework dynamically supports changes, and is capable of adapting itself to changing market related conditions and client demands â€“ even late during the development process. New features can be introduced to enhance the productâ€™s business value, and redundant functionality can be safely "removed" from the production plan without affecting the productivity levels.
Waterfall does not support, nor advocate, any types of changes once the documentation process is carried out, and the project commences. The framework is rigid and there is no scope of changing the functionality stated in the documentation process â€“ even if the client so demands.
In Agile, development is carried out by splitting the actual product into smaller developable parts known as "user stories" or product items. Right from the project conception stage, each user story is segregated and arranged depending upon its importance and business value. User stories having a greater business value or importance in the project are developed first, followed by less important ones. Thus during the Agile process, only important product features are developed at all times, thereby increasing the business value linked with the project currently underway.
Waterfall does not have features that can account for or take into consideration the current business value linked with the project. The concept does not exist. Projects are developed in a traditional manner, and no efforts are made to determine what they are currently worth in the market.