The History of Agile for Developers

Agile software development is widely accepted as the premier style of project management today. However, this was not always the case. Not two decades ago, Agile was yet to be created. More traditional methods of software development, such as waterfall, were used by most organizations. The rise to popularity of Agile is a consequential story. Developers and their role in software development are possibly the most affected by the history of Agile.

Waterfall Development History

Before Agile software development, waterfall was the preferred method of project management. The name comes from the way a product cascades through stages in one direction. At the most basic level, the steps of waterfall software development are requirements, design, implementation, verification, and maintenance. While some of these may sound similar to the steps of Agile software development, the fact that they only happen once per project is the key difference.

Waterfall Development Requirements

Requirements are set early and are difficult or impossible to change later. Customers must give an accurate depiction of what they want before they ever see any working software. Once development has begun, customers cannot change their minds since their requirements have already been committed. For developers, requirements will ultimately become programming assignments. Even if individual requirements turn out to be much more work than anticipated or generally bad ideas, they are part of the project and must be finished.

Similar to the requirements phase, the design is completed fully for all parts and features of a product. The development team must map out exactly how everything will be created, and stick to this plan. While planning and research are useful, it is cumbersome to require that a design is set in stone from the beginning. Developers occasionally find more efficient ways for a feature to work after development has begun. Since waterfall relies on all pieces fitting together the same way from start to finish, developers may be unable to make these changes. Their hands are tied, since revisiting requirements and design are often unfeasible.

59 Seconds Agile - The History of Agile

59 Seconds Agile – The History of Agile

Waterfall Development Implementation

Implementation, the step in which developers actually write code, is very rigid and inconvenient in waterfall development. Instead of allowing developers the creativity to make the code work in the way they see fit, they must stick to the completed design. Inevitably, this means that programming takes longer to finish. Also, developers might be less familiar with the design than what they may have chosen to use otherwise. This leaves them without as firm of an understanding of the code and often results in programming errors.

Waterfall Development Verification

Verification makes sure that software is working the way it was intended to. Software products can be extremely complex and may interact with unfamiliar applications, so the potential for bugs and issues with the product is high.  The developers need to fix these before it goes to customers. The problem with verification in waterfall development is how quickly technical debt builds up, and how difficult it can be to address. Since everything up to this point sticks to the original requirements and design, changes and fixes must also keep up with documentation from the very beginning of the process. This can make an ideal fix hard to come up with, and increase the time it takes to implement. Developers in waterfall have fewer tools at their disposal and are thus less efficient at fixing bugs.

Prev <— Continue Reading —> Next

Our Favourite Agile Books

Read Our Reviews

The History of Agile For Developers

Prior to the 1990’s software development was very slow, often taking years to complete development and release the product to market. The industry was following a very formal methodology for products and software development…

Read More

What is Agile to the Developer?

While traditional project management is still widely used, the benefits of an Agile approach to running a project are becoming more and more recognized. Where Agile has a distinct advantage over classic project management is the development of new products…

Read More

Why Use Agile as a Developer?

When determining if a move to Agile is right, a PESTLE can be used to simplify what factors should be considered. While Agile is sometimes thought of as a software development project management method, it isn’t just for these types of technology-centric companies…

Read More

The Agile Manifesto For Developers

Agile is a quick, simple, lightweight and effective way of managing projects. In traditional project management models…

Read More

The Agile Principles For Developers

When the Agile Manifesto was drawn up in 2001, it embodied four values and twelve principles that signaled a new approach to…

Read More

The Agile Fundamentals For Developers

Thinking of becoming a Scrum Master? Or are you already one, but you’re still new to the job? No matter what level of experience…

Read More

The Declaration of Interdependence For Developers

The Declaration of Interdependence establishes that all members, stakeholders, and customers are interdependent and…

Read More

The Agile Frameworks For Developers

There are many different Agile frameworks – all of them share the same philosophy and are built around the Agile Manifesto and Principles. But they vastly differ in their approaches, values, and structure. …

Read More

The Scrum Framework For Developers

The Agile Scrum framework is designed to deliver products and projects of any size. This includes projects, programs, and portfolios. Scrum provides guidelines on delivery techniques, events, and roles. Many of the same ceremonies are held within both a standard Agile scrum project and an Agile Scrum…

Read More

The Scrum Roles For Developers

Scrum is a useful tool for the creation, maintenance, plan, and execution of diverse products and services. The tool consists of…

Read More

The Scrum Team Size For Developers

The basics of Scrum can be easy but implementing them and succeeding with Scrum can be infinitely harder. Scrum …

Read More

The Agile Project Vision For Developers

At the heart of any great product is a great vision. It describes the primary goal or goals of a product and creates a focus that…

Read More

Forming the Scrum Team For Developers

Scrum is a framework that encourages delivery of potentially shippable product increments every 2-6 weeks. The work is…

Read More

Developing Epics For Developers

The term ‘epic’ in agile refers to a large user story that has not yet been defined in detail. Typically, an epic will cover a single…

Read More

The Agile Product Backlog For Developers

A Product Backlog is an organized collection of the existing User Stories (aka Wants and Needs) for an explicit business endeavor. Think of a shopping catalog of User Stories, ordered by urgency, that can be perused and selected from to determine what will be worked on during the current…

Read More

Release Planning For Developers

Although flexibility and adaptability are part and parcel of an agile methodology, this does not mean that no planning is required when…

Read More

Creating User Stories For Developers

User Stories are an integral part of the agile development process. They are an important agile technique that is used to frame…

Read More

Estimating User Stories For Developers

One of the principles of self-managing teams in Agile Scrum is working collaboratively with the Product Owner to effectively deliver…

Read More

Creating Tasks For Developers

According to The Agile Manifesto: “The best architectures, requirements, and designs emerge from self-organizing teams.” As a…

Read More

Estimating Agile Tasks For Developers

In Scrum, a list of user stories is produced and put together to form a product backlog, and each of these user stories will need to…

Read More

Creating the Sprint Backlog For Developers

The Sprint Backlog is defined as a group of user stories that are grouped together during the Sprint Planning Meeting. This…

Read More

Creating the Deliverables For Developers

Agile Scrum provides the framework for delivery of the vision of an organization. Execution of the vision includes processes, ceremonies and project deliverables that are also known as artifacts…

Read More

The Daily Stand-Up For Developers

The daily scrum is an opportunity for developers or anyone committed to working in the sprint to talk to each other to make sure the…

Read More

Product Backlog Prioritisation For Developers

The product backlog is a key element of Agile software development. It facilitates a development environment that creates valuable features and products for stakeholders…

Read More

The Sprint Review Meeting For Developers

The Sprint Review meeting comes at the end of the sprint and the goal of this meeting is to have key people in the room to be able …

Read More

Demonstrating and Validating the Sprint For Developers

As organizations migrate to Agile principles, there may be questions about how the organization can prove that there is value…

Read More

The Sprint Retrospective For Developers

A very simple step by step guide to help you choose the appropriate product development methodology from…

Read More

Releasing the Product For Developers

One of the most important milestones any project will ever have is finally releasing their product and putting it out there. It’s the…

Read More

Regression Testing For Developers

In companies using agile development, it is common to introduce changes in a product incrementally. Along with the new changes, unexpected issues may arise, testing whether the existing functionality is broken or not becomes very important…

Read More

Product Owners

Find out more about the Agile and the Product Owner Role

Read More


Find out more about the Agile and the Developer Role

Read More

More Articles

Read More

Chicken Appreciation Society

Translate »