Scrum vs Waterfall vs Agile vs Lean vs Kanban

There are a number of different approaches in the software development industry – some are new takes on old methods and others have adapted a relatively new approach. The two most commonly used methods in this field are the Agile such as, Scrum, Kanban and Lean and etc., and traditional Waterfall models such as structured methods or newer RUP.

Most software companies that follow these two models will argue that their chosen method is superior in respects, so before we answer the question, “Which one is more successful? We should look at their main differences.

Waterfall Approaches

Waterfall is a linear approach to software development process. Each of these represents a distinct phase of software development, and each phase generally finishes before the next one can begin. There is also typically a milestone between each development phase.

  • Structured as one big project in a sequential process
  • Suited for situations where change is uncommon
  • A process that requires clearly defined requirements upfront

Thus the waterfall model maintains that one should move to a phase only when its preceding phase is reviewed and verified as shown in the Figure below:

Waterfall approach
Waterfall approach

Best Scrum Software

Best Scrum Software Every Project Needs

A powerful scrum software that supports scrum project management. It features scrum tools like user story map, product backlog management, sprint backlog management, task management, daily scrum meeting, sprint planning tool, sprint review tool, sprint retrospective tool, burndown, impediment, stakeholder and team management.

Learn More

For example:

In Royce’s original waterfall model, the following phases are followed in order:

  • System and software requirements: captured in a product requirements document
  • Analysis: resulting in models, schema, and business rules
  • Design: resulting in the software architecture
  • Coding: the development, proving, and integration of software
  • Testing: the systematic discovery and debugging of defects
  • Operations: the installation, migration, support, and maintenance of complete systems

Agile Approaches

Agile is derived using Lean thinking that applies “Lean” concepts in the information technology environment. The key focus of the Lean approach is to:

  • Eliminate waste from processes
  • Minimize Business non-value added activities
  • Maximize added value from the consumer’s perspective
Agile Approaches
Agile Approaches

Agile approach is the proven project management methodology that encourages the following key concepts:

  • Frequent inspection and adaptation
  • A leadership philosophy that encourages team work, self-organization, and accountability
  • A set of engineering best practices that allow for rapid delivery of high-quality projects
  • A business approach that aligns development with customer needs and company goals

Agile Development – Iterative Lifecycle

Agile development stages include traditional planning, analyzing requirements, design, coding, testing, and deployment, but they form a cycle rather than a line. This means the processes are flexible, repeatable, can happen in any order and in parallel. This allows gathering the user feedback, continuous testing against different environments and changing the scope of the project on the run.

The Foundation of Agile Approaches

  • Empiricism – Ability to perform, stop, reflect, improve, and continue in a step-by-step process in efforts to increase productivity
  • Prioritization – Deliver work based on value to the business
  • Self-Organization – The team knows best how to deliver the work based on the resources and constraints
  • Time-Boxing – The team is required to complete the assigned tasks within the defined timelines.
  • Collaboration – The team commits to delivering the final products within the given timelines, which will encourage cross-team collaboration and ingenuity in completing the tasks.

Agile vs Waterfall – Scope, Time and Cost Triangle

The Waterfall Method’s greatest strengths are its fixed costs and predictability.  You know the price, and when it is going to be delivered.  Its most significant weakness is its inflexibility. The Agile Method is extremely flexible and could evolve into a significantly different product than was originally envisioned.

Agile vs Waterfall
Agile vs Waterfall

Traditional waterfall approach is built upon the basis of the triple constraints of time, cost and scope. Adjusting any of those variables forces a change in at least one of the others. Delivering a successful project is dependent on balancing these three competing variables. But as we know simply adding resources to a project doesn’t always bring about the desired goals.  As a matter of fact, if resources are added late on a software project, it actually has an adverse effect.

Agile Approach takes a different approach by turning the triple constraints upside down. Rather than viewing scope as fixed at the start, agile approach sets time (iterations) and cost (team members) as fixed; scope is then adjusted to focus on the highest priorities. Agile is built with the expectation that scope will evolve over time. The goal is to deliver the client’s most important requirements within the budgeted cost and time. Agile allows for new requirements or re-prioritization as the project moves forward.

Agile vs Waterfall quality
Agile vs Waterfall quality

Agile or Waterfall? See the Figures

The most recent report from the Standish Group covered projects they studied between 2013 to 2017. For this time period, the overall breakout of success, challenged and failure is shown below for agile and waterfall, with Agile projects being roughly 2X more likely to succeed, and 1/3 less likely to fail.

(Source: – Comparing Waterfall and Agile Project Success Rates)

Agile vs Waterfall - Project Success Rate
Agile vs Waterfall – Project Success Rate

The Agile Approach Umbrella

Since the birth of the Agile Manifesto in 2001, there has much buzz around being agile. In fact, Agile approach is just a way of thinking that enables teams and organizations to innovate, quickly respond to changing demand, while mitigating risk. Organizations can be agile using many of the available frameworks available such as Scrum, Kanban, Lean, XP and etc….

Scrum agile umbrella
Scrum agile umbrella

Lean Approach

A lean organization understands customer value and focuses its key processes to continuously increase it. The ultimate goal is to provide perfect value to the customer through a perfect value creation process that has zero waste.

5 Step Lean Approach

The five-step thought process for guiding the implementation of lean approach is easy to remember, but not always easy to achieve:

  1. Specify value from the standpoint of the end customer by product family.
  2. Identify all the steps in the value stream for each product family, eliminating whenever possible those steps that do not create value.
  3. Make the value-creating steps occur in tight sequence so the product will flow smoothly toward the customer.
  4. As flow is introduced, let customers pull value from the next upstream activity.
  5. As value is specified, value streams are identified, wasted steps are removed, and flow and pull are introduced, begin the process again and continue it until a state of perfection is reached in which perfect value is created with no waste.
5 steps Lean Approach
5 steps Lean Approach

Scrum Approach

Scrum is an agile way to manage a project, usually software development. Agile software development with Scrum is often perceived as a methodology; but rather than viewing Scrum as methodology, think of it as a framework for managing a process.

Scrum Process Canvas
Scrum Process Canvas

Kanban Approach

Kanban is Japanese for “visual signal” or “card.” Toyota line-workers used a Kanban to signal steps in their manufacturing process. As a part of Lean, the system’s highly visual nature allowed teams to communicate more easily on what work needed to be done and when. It also standardized cues and refined processes, which helped to reduce waste and maximize value. Similarly to a scrum sprint board, Kanban tracks ‘to do – Doing – done’ activities, but it limits them by the number of ‘work in progress’ activities (the number is defined by the team manager and cannot be exceeded).

Kanban Approach
Kanban Approach

There are four fundamental Kanban principles:

  • Visualize work to increase communication and collaboration.
  • Limit work in progress to avoid an endless chain of non-prioritized open tasks.
  • Measure and optimize the flow, collect metrics, predict future problems.
  • Aim for continuous improvement as the result of analysis.
About Visual Paradigm
Visual Paradigm help organizations stay competitive and responsive to change faster and better in today’s fast changing environment. Our award-winning products are trusted by over 320,000 users in companies ranging from small business, consultants, to blue chip organizations, universities and government units across the globe. It enables organizations to improve business and IT agility and foster innovation through popular open standards and process frameworks.Visual Paradigm, a killer Agile feature in 2018, introduced Scrum Process Canvas for automating the way a Scrum team to create, manage and deploy software application that empowers the team to continuously improve their performance at unprecedented speed and scale.

Manage the Entire Scrum Process in One Page

  • Automate the Scrum Framework in a fun and enjoyable dashboard with eye-catching updated status.
  • Manage Backlog, Multiple Sprints of different Scrum Roles with a single-page visually executable canvas
  • Allow instantly access, review and generate scrum artifacts and related documents to be archived in the Shared Cabinet
  • Automate the Scrum events and related activities with self-explanatory instructions, samples and required document templates.

Turn every software project into a successful one.

We use cookies to offer you a better experience. By visiting our website, you agree to the use of cookies as described in our Cookie Policy.