Agile is not a methodology — it is a set of values and principles that get operationalized into frameworks like Scrum, Kanban, and SAFe. Today you learn what Agile actually says (not what teams think it says) and why the distinction matters.
By the end of this lesson you will recite the four Agile Manifesto values and twelve principles, explain the core differences between Scrum, Kanban, and SAFe, identify the three Scrum roles and their accountabilities, and recognize anti-patterns that teams call Agile but are not.
Agile Manifesto is the foundation of Day 1. Every concept that follows builds on the mental model you establish here. The most effective approach is to understand the principle first, then apply it — skipping straight to implementation creates gaps that compound into confusion later.
Work through each example in this lesson sequentially. The concepts connect, and the order is deliberate. If something is unclear, slow down at that point rather than pushing past it — a ten-minute pause now saves hours of debugging later.
Understanding Agile Manifesto requires seeing it in motion. The code below is not a complete application — it is a minimal, working illustration of the key mechanism. Study the pattern, run it, break it deliberately, then fix it. That cycle builds real comprehension.
Once the basic pattern works, the logical next step is Scrum vs Kanban vs SAFe. This is where the abstraction becomes useful — you move from understanding the mechanism to applying it to real problems. The transition is usually smaller than it feels. Most of the hard work happened in Section 1.
roles completes today's picture. It is where Agile Manifesto and Scrum vs Kanban vs SAFe converge into a pattern you can apply to novel problems. This integration step is often where the day's learning consolidates — if the earlier sections felt abstract, this one typically makes them click.
Implementing Agile Manifesto alone handles the happy path. Real systems encounter edge cases, invalid input, and unexpected state. Missing Scrum vs Kanban vs SAFe means missing those guards.
Combining Agile Manifesto with Scrum vs Kanban vs SAFe gives you a complete, defensible implementation. The extra lines cost ten minutes; the robustness they add is worth hours of debugging time.
Several mistakes appear consistently when engineers encounter Agile Foundations for the first time. Recognizing them now costs nothing; encountering them in production costs hours.
Two intensive days (Thu–Fri) with an instructor who has taught thousands of engineers. Cohorts in 5 cities, June–June–October 2026 (Thu–Fri).
Reserve Your Seat — $1,490Before moving on, you should be able to answer these without looking: