Summary -

In this topic, we described about the below sections -

What is Agile?

The methodology which works on continuous iteration development and testing throughout the SDLC. Agile process would provide continuous feedback which helps to implement the customer needs and requirements.

The main objective of Agile is to produce a working product at the end of every iteration.

What is Kanban?

Kanban is a kind of dashboard called as 'Kanban Board'. It displays the workflow of tasks. It is a method used to manage, define, and improve services for delivering knowledge. Team members can see the progress of work at every stage of development.

Agile Principles

  • The goal is to achieve customer satisfaction by offering continuous improvement in delivery.
  • Changes are always welcome even in later stage.
  • Delivering working software at end of every iteration.
  • Agile method promotes sustainable development.
  • Technical expertise is always on top.

Kanban Principles

  • Kanban visualizes workflow which is easily understandable
  • Acts of leadership is always encouraged at all levels.
  • Measures and improves collaboration.
  • Helps the teams to make the process easy and explicit.


Agile Vs Kanban
Agile Kanban
Adapting changes as per the requirements which change dynamically. Wastage reduction and removing the activities that never add value to the project.
Breaking the entire project into smaller chunks helps to focus on the high-quality development, testing and collaboration. Short period cycles can deliver features faster.
Focuses mostly on constant communication. Breaking down the tasks into smaller parts makes the items to fit in within the boundaries.
Here, the goal is to Continuously development and test. The goal of Kanban is to improve process.
The process is dependent on User Story boards. The process depends on Kanban boards.
Changes can be made at anytime in the project as there are shorter cycles. Rapid feedbacks help the team to get motivated and improve performance.
Agile process allows iterative Development. Kanban does not allow iterative Development.
It does not provide support to visually check the work which is in-progress. Allows to check the work in-progress visually.
Sprint planning consumes the team's time for an entire day. Takes less organization set up changes to get started.
If shorter planning cycles, changes can be easily accommodated at anytime during the project management. Continuous feedback loops result in a more motivated, empowered and actively performing team members.
Agile would require more organizational setup. Kanban needs very less organizational setup.
In Agile, breaking the project into small chunks would help the team to focus on high quality development, testing and collaboration. In Kanban, smaller time cycles would deliver features faster.