| # | Agile | Kanban |
| Cadence | Regular Fixed length Sprint, May be 2 week | Continues flow |
| Release methodology | At the end of each sprint | Continues delivery |
| Roles | Product Owner, Scrum Master, Development Team | No Required roles |
| Key Metrices | Velocity | Lead Time, Cycle Time, WIP |
| Change Philosophy | Teams should not make changes during the sprint | Changes can happen at any time |
| Planning | Sprint planning can consume the scrum teams time for an entire day | Need very less organisation setup changes to get started |
| Segmentation | Project divide into defined smaller segment with planning and provide high quality product | Project divide in ad-hoc manner and at the end product quality normally not upto the mark, since testing not happen proper manner. |
| Effort | It’s is easy to identify the estimation of complete project timeline via team velocity | There is no such end point defined of the product, estimation of complete product can not be defined. |
| | |