Методологии и процесс разработки

How a team moves from an idea to a working product is a question no less important than the code itself. This section covers approaches to organizing development: why the industry moved away from the rigid "waterfall" toward flexible iterations, how Scrum differs from Kanban, which engineering practices make frequent releases safe, and how all of this works when there isn't just one team but dozens.

• Development models: from Waterfall to Agile — How approaches have evolved: Waterfall, the V-model, iterative development, and Agile as a set of values. Where each one breaks down and how to choose one for the job.
• Scrum: roles, events, and artifacts — Sprints, roles (Product Owner, Scrum Master, the team), the backlog, Definition of Done, and Scrum events — plus the common mistakes teams make when adopting it.
• Kanban: flow, WIP limits, and pull — Managing the flow of work on a board, why limiting work in progress speeds up delivery, and when Kanban is a better fit than Scrum.
• Extreme Programming: the engineering practices of Agile — TDD, pair programming, continuous integration, and refactoring — the practices that make fast iterations safe for quality.
• Estimation and planning: story points and velocity — Why teams estimate in story points rather than hours, how Planning Poker and velocity work, and why velocity must never be turned into a KPI.
• Scaling Agile: SAFe and LeSS — What to do when dozens of teams work on one product: SAFe, LeSS, and why you remove dependencies first and add ceremonies second.