On 12 December, 2025, around 50 practitioners and leaders gathered in Hilversum, The Netherlands, with a shared feeling that something in the Agile conversation had stalled. Agile practices are widespread, certifications abound, and yet many organisations seem to be experiencing more control with less learning, and growing fatigue rather than adaptability. Instead of introducing another model or defending past approaches that once helped, this workshop created space to pause and ask more uncomfortable questions: what have we lost along the way, what tensions are we no longer naming, and what might agility need to become in a world shaped by scale, governance, and AI?<\/p>\n\n\n\n
The session was co-organised by local practitioners together with members of the Agile Alliance Supporting Agile Adoption initiative<\/a>, and facilitated by Jeannie Flynn. Rather than a conference or panel discussion, the afternoon was structured around small, self-directed groups working on \u201cwicked problems\u201d (the kinds of challenges that don\u2019t have clear owners or clean solutions). Over four hours, participants explored themes ranging from leadership and scaling to governance, innovation, and the impact of AI, capturing their thinking on walls and posters to make sense of what\u2019s actually happening in organisations today.<\/p>\n\n\n\n Across the conversations, a consistent pattern emerged: many of the tensions now attributed to \u201cAgile\u201d sit outside the reach of teams, frameworks, or roles. Participants repeatedly surfaced mismatches between speed and learning, strategy and behaviour, governance and value, human judgement and automation, short-term delivery and long-term intent. In several groups, frameworks, scaling approaches, and past Agile adoptions were described as having, at times, simplified complex problems, sometimes turning principles into rules and learning into compliance. The shared insight wasn\u2019t that leadership failed agility, but that agility was often asked to operate inside unresolved organisational constraints. As these constraints become impossible to ignore, looking away (or worse, hiding behind Agile) is no longer an option.<\/p>\n\n\n\n What follows is a snapshot of what participants chose to explore. <\/em><\/p>\n\n\n\n People in this group questioned whether organisations are still being run as machines, while expecting people to behave as if they were part of a values-based system. They named authoritarian leadership not as a personality flaw, but as a reaction to threat, reinforced by a gap between leaders and doers and deeply held assumptions about what \u201cgood management\u201d looks like. Agility, they argued, requires leaders at all levels<\/em> to shift from designing work to developing people\u2019s capability, creating spaces to learn how to deal with uncertainty and to be explicitly judged on becoming wiser tomorrow than today<\/em>.<\/p>\n\n\n\n This group surfaced what they experienced as a fundamental mismatch: organisations celebrate speed and delivery, while crowding out learning and innovation. Innovation was mapped across time (from cash cows to new ideas), showing how short-term pressure, top-down decisions, budget, fear, risk, and being \u201ctoo busy\u201d repeatedly block progress. Rather than calling for more process, the group pointed to an entrepreneurial mindset, lightweight frameworks, and the explicit balancing of discovery, delivery, and product as ways to keep innovation alive – suggesting that innovation doesn\u2019t disappear as organisations scale; it gets deprioritised.<\/p>\n\n\n\n This group explicitly rejected the idea that scaling is a solution in itself. \u201cScrum is designed for teams,\u201d they noted, and scaling without first addressing mindset, culture, and context simply reproduces hierarchy while calling it Agile. They challenged one-size-fits-all approaches, pointing out that even within a single organisation, contexts differ. And language matters! Rather than focusing on scaling frameworks, the conversation shifted toward shared principles, coherent steering, and first steps that create satisfaction and vision, because without those, resistance is the predictable outcome.<\/p>\n\n\n\n People in this group argued for a clear inversion: guidelines over frameworks, pragmatism over dogma, co-creation over enforcement, and evolution over stagnation. Frameworks were positioned as a starting frame<\/em>, not a fixed future – useful only insofar as they enable learning and adaptation. One provocation was explicit: when frameworks stop evolving and start being enforced, they move from enabling agility to actively limiting it.<\/p>\n\n\n\n Here, the conversation challenged the idea that governance is the enemy of agility, arguing instead that the real problem is confusion: governance, compliance, risk management, and legislation are repeatedly conflated. They surfaced a lack of shared definition of both governance<\/em> and business value<\/em>, alongside a disconnect between delivery teams and those setting governance constraints. Rather than bypassing governance, the focus shifted to making decision-making, rules, measures, and value explicit, and to sharing real success and failure stories – suggesting that agility breaks down not because of governance, but because its purpose and value are poorly understood.<\/p>\n\n\n\n This group framed the next 1\u20133 years as a shift toward human + AI collaboration, not automation replacing people. The conversation moved deliberately from the individual (\u201chow will my<\/em> role change?\u201d) to teams revisiting how they collaborate, and then to organisational change management. Trust, safety, data management, security, and ethics surfaced as non-negotiables. Rather than rewriting Agile, the group returned to the Agile values, arguing that as processes speed up and tools proliferate, individuals and interactions <\/em>(trust, experimentation, customer collaboration, and responding to change) become even more critical.<\/p>\n\n\n\n This group framed the tension not as Agile versus project management, but as a disconnect between strategy and behaviour<\/strong>. Two questions dominated: \u201cWhat\u2019s our strategy?\u201d<\/em> and \u201cWhat\u2019s our mindset or behaviour?\u201d<\/em> – suggesting that without alignment on intent and how people act, neither Agile practices nor project controls can close the gap. The provocation was clear: integration fails not because of methods, but because strategy and behaviour are treated as separate conversations.<\/p>\n\n\n\n This group questioned whether AI changes how leaders work<\/em>, or whether it fundamentally changes what leadership is. They surfaced a distinction between formal authority, decision rights, and leadership, asking what remains human work when tasks, information, and recommendations are increasingly automated. As AI takes over coordination, analysis, and execution, some leadership activities may disappear, while others emerge: sense-making, ethical judgment, cultivating human connection, setting boundaries, and shaping shared context. The provocation was explicit: AI doesn\u2019t just support leadership – it may redistribute power, redefine decision-making, and force leaders to let go of certainty.<\/p>\n\n\n\n Reimagining Agility wasn\u2019t about finding answers or even agreeing. It was about creating space to surface tensions that many people are already living with but rarely get time to explore together. What emerged wasn\u2019t a roadmap, but a reminder: these conversations don\u2019t belong to conferences, consultants, or certification bodies. They belong with practitioners, leaders, and teams willing to sit with complexity and learn in public. <\/p>\n\n\n\n Sign up to stay connected<\/a>, and let us know if you’d like to host a similar Reimagining Agility<\/a> workshop in your area. Learn more now<\/a>.<\/p>\n\n\n\n <\/p>\n","protected":false},"excerpt":{"rendered":" On 12 December, around 50 practitioners and leaders gathered in Hilversum, The Netherlands, with a shared feeling that something in the Agile conversation has stalled. What follows are the workshop’s findings on how we can work to reimagine Agile.<\/p>\n","protected":false},"author":5048037,"featured_media":8102961,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_tec_requires_first_save":true,"_EventAllDay":false,"_EventTimezone":"","_EventStartDate":"","_EventEndDate":"","_EventStartDateUTC":"","_EventEndDateUTC":"","_EventShowMap":false,"_EventShowMapLink":false,"_EventURL":"","_EventCost":"","_EventCostDescription":"","_EventCurrencySymbol":"","_EventCurrencyCode":"","_EventCurrencyPosition":"","_EventDateTimeSeparator":"","_EventTimeRangeSeparator":"","_EventOrganizerID":[],"_EventVenueID":[],"_OrganizerEmail":"","_OrganizerPhone":"","_OrganizerWebsite":"","_VenueAddress":"","_VenueCity":"","_VenueCountry":"","_VenueProvince":"","_VenueState":"","_VenueZip":"","_VenuePhone":"","_VenueURL":"","_VenueStateProvince":"","_VenueLat":"","_VenueLng":"","_VenueShowMap":false,"_VenueShowMapLink":false,"_tribe_blocks_recurrence_rules":"","_tribe_blocks_recurrence_description":"","_tribe_blocks_recurrence_exclusions":"","ep_exclude_from_search":false,"_jf_limit_responses":"","footnotes":""},"categories":[182,183],"tags":[],"content_source":[],"class_list":["post-8102951","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-community","category-the-alliance"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/posts\/8102951","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/users\/5048037"}],"replies":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/comments?post=8102951"}],"version-history":[{"count":12,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/posts\/8102951\/revisions"}],"predecessor-version":[{"id":8102975,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/posts\/8102951\/revisions\/8102975"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/media\/8102961"}],"wp:attachment":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/media?parent=8102951"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/categories?post=8102951"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/tags?post=8102951"},{"taxonomy":"content_source","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/content_source?post=8102951"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}What patterns showed up across the room<\/strong><\/h3>\n\n\n\n
Creating Agile leadership & culture<\/strong><\/h3>\n\n\n\n
Fostering innovation & continuous learning<\/strong><\/h3>\n\n\n\n
Scaling Agile across organisations<\/strong><\/h3>\n\n\n\n
The future of frameworks<\/strong><\/h3>\n\n\n\n
Aligning Agile with business value & governance<\/strong><\/h3>\n\n\n\n
AI and automation<\/strong><\/h3>\n\n\n\n
Bridging Agile and traditional project management<\/strong><\/h3>\n\n\n\n
The impact of AI on leadership<\/strong><\/h3>\n\n\n\n
Where this leaves us<\/strong><\/h3>\n\n\n\n
Keep the conversation alive! <\/h3>\n\n\n\n