The cross-cutting concepts of agile, beyond Scrum and Kanban: the agile manifesto and values, agile delivery, agile at scale (Enterprise Agile), and an overview of agile frameworks. A foundation for understanding why and how organizations adopt agile, before specializing in a specific framework like Scrum or Kanban.
Agile relies on a precise set of values and principles — the 2001 agile manifesto lists 4 values and 12 principles — but also on notions that are easy to mix up when spoken out loud: agile delivery, agile at scale, Lean, DevOps. Without a solid grasp of this vocabulary, it's difficult to clearly explain why an organization chooses agile over another approach.
Flashcards with spaced repetition are particularly well suited to this kind of conceptual content: every card forces an active recall of the exact definition, rather than an approximate recognition. The FSRS algorithm reschedules each card at the optimal moment, which reduces the review time needed to retain these concepts durably.
This category deliberately comes before Scrum and Kanban in the recommended path: it sets the conceptual frame (why agile) before you dive into the concrete detail of a framework (how to apply it day to day).
It's also useful for non-technical roles that work alongside agile teams — managers, HR, finance — who don't need to master Scrum in detail but do need to understand the big principles to collaborate effectively.
Much of the confusion comes from the fact that agile is often reduced to a single framework (usually Scrum) in everyday language. In reality, agile is a set of values and principles that can take shape in several different frameworks, and an organization can be agile without following Scrum to the letter. Clarifying this distinction upfront avoids plenty of misunderstandings in meetings.
Four subtopics cover cross-cutting agile concepts, from the founding manifesto to agile at scale.
The 4 values and 12 principles of the 2001 agile manifesto — the conceptual foundation shared by every agile framework, originally written by 17 software development practitioners.
Iterative and incremental delivery, short feedback loops, continuous improvement — the mechanisms that set agile apart from sequential approaches where everything is specified upfront.
Coordinating several agile teams within the same organization: strategic alignment, cross-team dependencies, release synchronization and portfolio-level governance.
An overview of the agile approaches that complement Scrum and Kanban in the agile delivery ecosystem, useful to place different methodological frameworks relative to each other.
A path that moves from general principle to concrete application.
The agile manifesto is the common reference for every framework — the logical starting point of this category.
Once the values are in place, agile delivery explains how they translate concretely into a team's day-to-day rhythm of work.
Useful if you work in an organization with several agile teams to coordinate, or if you're aiming for a coordination role.
Once this category is consolidated, the Scrum and Kanban category lets you move from concept to the concrete framework most agile teams use day to day.
Agile Methods covers concepts that cut across agile in general (values, principles, delivery, agile at scale). Scrum and Kanban covers the two most widely used frameworks specifically, with their concrete roles, events and practices.
No, it's the other way around: this category lays the conceptual groundwork of agile, which makes Scrum and Kanban easier to understand afterward.
No. The concepts covered here (values, principles, agile delivery) are useful to any role working alongside agile teams, technical or not — managers, HR, finance, project leadership.
It's the set of practices that let you coordinate several agile teams within the same organization while keeping strategic alignment and managing dependencies between teams — a different challenge from agile at the single-team level.
Yes, this category exists in both English and French, with the same 4-subtopic breakdown in each language.
With 15 to 20 minutes a day, most learners see solid initial retention within a few weeks. The FSRS algorithm adapts the pace to how consistent you are.
Two natural next steps: Scrum and Kanban to move to the concrete detail of a specific framework, or Product Owner if your role leans more toward product than delivery.
Mainly to shorten feedback loops and adapt faster to a need that evolves along the way — at the cost of less detailed upfront planning than a classic predictive approach. It's not a value judgment: the choice depends on context, the nature of the product, and the level of uncertainty involved.
This category focuses on agile concepts in the sense of the manifesto and agile delivery. DevOps is a complementary discipline, centered on deployment automation and continuous integration, which isn't covered in detail here.
Yes. Being agile is primarily about applying the manifesto's values and principles — iterative delivery, fast feedback, continuous improvement. A team can embody these principles through a custom process that doesn't map exactly onto Scrum or Kanban.
No, though it originated there. The manifesto and its values have since been adopted well beyond software — marketing, HR, hardware and even some public-sector teams use agile principles to organize iterative, feedback-driven work.
Access the decks in the Agile Methods category, free and premium.
See the decks