What is Agile: principles, Scrum vs Kanban, when it does harm

In practice, the loop is built from concrete practices: sprints provide delivery cadence, retrospectives create a mechanism for improvement, and TDD, pair programming, and code review maintain quality through frequent change. The core principle is simple: a working product matters more than a status report. A line-by-line breakdown of all 12 principles is in the article. 12 Agile Principles for Business.

Among Agile teams, Scrum is the most used framework (87%), with Kanban second (56%), according to the State of Agile summary. They are not rivals in an either-or choice: Scrum sets the sprint cadence, while Kanban manages continuous flow. Below is a one-screen comparison, and a deeper Waterfall comparison is in the article. Scrum, Kanban and Waterfall: How to choose a methodology.

Scrum and Kanban cover most teams, but not all. Three families solve problems beyond the basic frameworks: engineering discipline, scaling to dozens of teams, and extending flow to infrastructure and data.

A "pure" framework is rarely seen in production: 74% of organizations use mixed models - Scrum plus Kanban plus SAFe and others (State of Agile, summary). Waterfall is not dead; it is merging with Agile: the share of Agile+Waterfall hybrid projects rose from 20% (2020) to 31.5% (2023), according to PMI Pulse of the Profession (summary), and about 27% of teams use ScrumBan.

How the hybrid works and when it is more honest than pure Agile - in the article Agile and Waterfall: hybrid project management.

The biggest change over the past year is not a new framework, but AI inside the existing ones. The share of Agile teams using AI in their work rose from 68% to 84% in a year (Digital.ai, 18th State of Agile Report, summary) - the sharpest annual increase in the survey's history. AI speeds up sprint routine: drafts of user stories and acceptance criteria, backlog review, and code review suggestions. It is a layer on top of Scrum and Kanban, not a replacement for the feedback loop: priorities, customer agreement, and accountability for results remain with people.

Agile methods have long moved beyond software development. In marketing, campaigns run in short iterations with A/B tests and rapid feedback; in HR, hiring is managed with sprints and Kanban boards; in finance, banks break complex initiatives into increments and test them with pilot groups. The scale is real: 86% of marketers plan to move teams to Agile approaches, and according to Gartner (summary), 63% of HR leaders already use Agile methods.

The same caveat applies as in IT: highly regulated manufacturing and certifiable processes work better with Waterfall or a hybrid.

After Jira and Trello left the CIS market, teams moved to domestic trackers and self-hosted boards - tool choice became part of import substitution. The specifics depend on the security perimeter and budget, so the principle matters more than the brand: Agile is not a board, but a feedback loop, and it can be moved to any tracker. When migrating, look at what actually affects flow: WIP control, change history, CI/CD integrations, and data retention requirements, not the product name.

The main barrier to adoption is not tools but people: 47% cite organizational resistance and culture clash as the main obstacle to Agile transformation (State of Agile, summary).

Typical pitfalls: top-down resistance, when managers fear losing control; pseudo-Agile, where meetings are simply renamed as a daily, but there are no values or self-organization; no Product Owner, which leads the team to do unnecessary work; an incentive system based on individual KPIs, which breaks teamwork; and a distributed team without clear communication rules.

The foundations of Agile appeared long before the manifesto: as early as the 1980s, Japanese manufacturers, including Toyota, were developing lean manufacturing - waste reduction, self-organizing teams, continuous improvement. These principles were transferred to software development, and in February 2001 a group of engineers formulated the Agile Manifesto: 4 values and 12 principles. Today, Agile is not a specific set of practices, but a culture of adaptability; outside IT, it is used in marketing, HR, finance, and education.

Verification date: 2026-07-08. External links are provided as plain text.

Digital.ai - 18th State of Agile Report 2025 (AI 84%, hybrid 74%): digital.ai/state-of-agile · summary at peakdigital.online/reports/state-of-agile-2025-ai-adoption-governance Businessmap (Kanban University) - Agile Statistics 2026 (Scrum/Kanban shares, PMI success, hybrid, 47% barrier): businessmap.io/blog/agile-statistics PMI - Pulse of the Profession 2023/2024 (Agile success about 75% in 2023, hybrid 31.5%, industries): pmi.org/learning/thought-leadership/pulse Engprax / Dr Junade Ali and J.L.

Partners, 2024 - 268% higher failure, 65% failure rate, 97% with clear requirements (consider customer bias): engprax.com/post/268-higher-failure-rates-for-agile-software-projects-study-finds The Register - independent summary of the Engprax study: theregister.com/2024/06/05/agile_failure_rates StarAgile - State of Agile 2026 (adoption 94-97%, maturity): staragile.com/blog/state-of-agile eSparkinfo - 60+ Agile Statistics 2026 (Agile beyond IT: marketing/HR/finance): esparkinfo.com/blog/agile-statistics