The Scrum Dominance and Mainstream Adoption era (2005-2010) was the period in which Agile moved from "alternative approach adopted by forward-thinking teams" to recognized mainstream practice, and in which scrum emerged as the dominant Agile framework by a substantial margin. The mechanisms of this dominance — principally the scrum-alliance's Certified Scrum Master program — also seeded the certification economy that would define the next era and eventually draw the movement's most pointed critiques.
Scrum's Rise to Dominance
The scrum-alliance's CSM program was the primary engine of Scrum's dominance. Between 2005 and 2010, the two-day-course-plus-certification model produced hundreds of thousands of certified practitioners, creating a self-reinforcing cycle: demand for Scrum trainers grew, which produced more trainers, which produced more certified practitioners, which increased organizational adoption, which created more demand for practitioners. By 2010, "Agile" and "Scrum" had become functionally synonymous in many organizational contexts.
Scrum's design was well-suited to this adoption dynamic. Its framework is minimal: three roles (Product Owner, Scrum Master, Development Team), three artifacts (definition-of-done, Product Backlog, Sprint Backlog), five events (sprint-planning, Sprint, daily-standup, sprint-review, retrospective). This minimalism made it easier to explain, teach, and certify than the more comprehensive extreme-programming — and easier for organizations to claim adoption without deep change to their management structures.
XP's Fate: Practices Adopted, Brand Faded
extreme-programming experienced an inverse trajectory. XP's technical practices — test-driven-development, continuous-integration, pair-programming, refactoring, collective-code-ownership — were widely adopted, often by teams calling themselves Scrum teams. But XP as a named, branded methodology faded from organizational discourse. Few teams in this period called themselves "XP teams"; many practiced XP practices within Scrum structures.
This produced an irony: XP's technical practices arguably spread further in this era than at any point before, but they spread anonymously, attached to Scrum's organizational scaffolding rather than to Beck's original framework. The xp-explained-second-edition had already adjusted XP to acknowledge this; robert-c-martin's clean-code (2008) propagated XP's craft values without the XP brand.
Kanban Enters the Agile Space
During this era, David Anderson's application of Kanban to software development (beginning approximately 2004-2007, with his work at Microsoft and Corbis) established Kanban as an alternative to Scrum for teams seeking an evolutionary rather than prescriptive approach. Kanban's entry into Agile discourse was gradual but significant: it offered WIP limits, flow management, and information-radiators as a toolset that could be overlaid on existing processes rather than replacing them — a much lower adoption barrier than Scrum's full framework replacement.
Clean Code and the Craft Movement
robert-c-martin's clean-code (2008) was a significant text of this era, establishing the software craftsmanship values that Martin and others would later articulate as a movement. Clean Code applied extreme-programming's technical discipline (rigorous refactoring, meaningful naming, small focused units) to the broader audience of practitioners who might never identify as XP practitioners. It reinforced the argument — implicit in XP, explicit in craftsmanship discourse — that working-software required engineering discipline, not just iterative process.
The Scrum Guide (2010)
The scrum-guide, first published by ken-schwaber and jeff-sutherland in 2010, was this era's closing institutional document. A brief (approximately 13 pages), freely available, normative definition of Scrum, the Scrum Guide was a deliberate counter to the accumulation of Scrum books, courses, and interpretations that the scrum-alliance era had produced. It said: this is Scrum; everything else is optional additions.
The Schwaber Split (2009)
The era closed with a significant institutional rupture: ken-schwaber's departure from the scrum-alliance in 2009. The schwaber-leaves-scrum-alliance-2009 dispute centered on the direction of the CSM certification — specifically, whether its attendance-based, low-barrier model was consistent with the rigorous, disciplined Scrum practice Schwaber had always advocated. Schwaber founded scrum-org as an alternative, with examination-based assessment rather than course attendance.
The split created two competing Scrum certification bodies and foreshadowed the broader critique — more fully articulated in the enterprise-scaling-era and post-agile-era — that Agile certification had become disconnected from Agile competence.
Transition to Enterprise Scaling
By 2010, Agile had won the argument at the team level. The question "should we use Agile?" was being replaced by "how do we scale Agile across the enterprise?" This shift in the dominant question — from adoption to scaling — defined the next era and created the market that dean-leffingwell's safe-scaled-agile-framework was designed to serve.