The period between 2010 and 2013 was a formative era for Scrumban within the Agile community, marked by increasing visibility and endorsement as a distinct Agile framework. Here's a detailed overview of this pivotal phase:

Growing Presence in Agile Events: During these years, Scrumban began to feature more prominently in Agile-centric conferences, workshops, and gatherings. Events such as the Agile Alliance's annual conference, regional Scrum Gatherings, and Lean Kanban conferences included sessions specifically dedicated to Scrumban. These forums served as a critical platform for practitioners to share experiences, discuss the nuances of the framework, and educate the wider community.

Workshops and Training Sessions: Focused workshops and training sessions on Scrumban started to emerge, facilitated by Agile coaches and thought leaders. These sessions provided hands-on opportunities for teams to learn about Scrumban practices, such as visualizing workflow, managing WIP, flow control, and enhancement techniques for Scrum rituals using Kanban metrics.

Emergence of Thought Leaders: During this period, a number of Agile coaches and thought leaders started to specialize in Scrumban, contributing to its body of knowledge through their practical experience. They played a vital role in addressing misconceptions, clarifying best practices, and demonstrating how Scrumban could be adapted to various contexts.

Expansion of Literature: In addition to conferences and workshops, the literature on Scrumban also expanded. Agile-related publications started to feature articles on Scrumban, and influential bloggers within the community often discussed the framework's benefits and challenges. This period also saw the publication of additional books and resources that helped to cement Scrumban's reputation as a valid and valuable approach to project management.

Case Study Presentation and Analysis: Case studies detailing the application of Scrumban in different environments were often presented at Agile events. These case studies provided empirical evidence of Scrumban's effectiveness and allowed practitioners to analyze real-world applications, successes, and failures.

Recognition as a Standalone Methodology: Scrumban's presence in such professional gatherings was indicative of its growing traction as not just an intermediary step between Scrum and Kanban, but as a standalone methodology. It became increasingly recognized for its unique advantages, particularly in scenarios where neither pure Scrum nor pure Kanban seemed to be the perfect fit.

Collaborative Improvement and Sharing: Agile gatherings during this time were not just about showcasing Scrumban but also served as incubators for collaborative improvement. Practitioners shared tools, strategies, and insights that contributed to the continuous refinement of the framework.

Integration with Other Agile Practices: The flexibility of Scrumban led to discussions on how it could be integrated with other Agile practices, such as Extreme Programming (XP) and Lean Software Development. These conversations further enriched the understanding and applicability of Scrumban across various domains.

Increased Adoption and Advocacy: As more organizations reported positive outcomes from using Scrumban, advocacy for the framework grew. The success stories presented at Agile events encouraged more teams to consider Scrumban as a viable option for managing their projects.

Development of Support Tools: The increasing interest in Scrumban also influenced the market of Agile project management tools. Tool vendors began to incorporate features that supported Scrumban practices, such as customizable Kanban boards and metrics like Cumulative Flow Diagrams and Lead Time charts.

The years between 2010 and 2013 were critical in the evolutionary timeline of Scrumban, as they witnessed the transition of the methodology from a niche concept to a recognized Agile framework. This period laid the groundwork for the further maturation and widespread adoption of Scrumban in the subsequent years.