{"id":8103977,"date":"2026-02-02T13:51:07","date_gmt":"2026-02-02T21:51:07","guid":{"rendered":"https:\/\/agilealliance.org\/?p=8103977"},"modified":"2026-02-07T17:45:39","modified_gmt":"2026-02-08T01:45:39","slug":"beyond-frameworks-four-shifts","status":"publish","type":"post","link":"https:\/\/agilealliance.org\/beyond-frameworks-four-shifts\/","title":{"rendered":"Beyond Frameworks: Four Shifts"},"content":{"rendered":"\n

Remember when Scrum solved all of your team’s problems? At the first sign of trouble, you just went back to the Scrum Guide and found all the answers inside. And remember when a company needed to scale: it was just a matter of applying SAFe, Nexus, or something similar, and everything was solved? Yeah, neither do I.\u00a0<\/em><\/p>\n\n\n\n

The truth is, we never had a one-size-fits-all framework. Over the years, this has become even more painfully evident. It\u2019s practically impossible to apply any framework fully by the book, sometimes because the organisation\u2019s structure won\u2019t allow it, sometimes because the work itself doesn\u2019t fit, or even because the team\u2019s unique culture and dynamics resist rigid prescriptions. <\/p>\n\n\n\n

That\u2019s why, together with three other Agile practitioners, I dove into the topic “The Future of Frameworks” — one of several wicked problems presented at the Agile Alliance\u2019s “Reimagining Agility: Shape the Future of Agile” workshop hosted at Nike EHQ in Hilversum, NL on 12 December 2025. (See more about Reimaging Agility here.<\/a>)<\/p>\n\n\n\n

Why this topic? <\/h2>\n\n\n\n

Frameworks give structure, help kick off and guide teams, and shed light on sensitive topics. But after so many changes in technology, companies, and the world, are they still the way to go in their current form? <\/p>\n\n\n\n

The challenge: adapt them, abandon them, or replace them with something more flexible for the future.<\/p>\n\n\n\n

It\u2019s a wicked problem because it hurts. Companies have poured millions into training, certifications, tools, and even new roles — all sold as the magic silver bullet to solve their organisational woes overnight and turbocharge delivery. <\/p>\n\n\n\n

Yet the core problems linger unsolved, leaving little beyond superficial compliance and dashed hopes for that promised transformation. <\/p>\n\n\n\n

There\u2019s emotional attachment, too. Frameworks that kick-started new ways of working became part of the companies\u2019 identity. “We do SAFe.” Change? No way!\u201d <\/p>\n\n\n\n

But what does the future (or indeed the present) demand?<\/p>\n\n\n\n

Questions that ignited the debate<\/h2>\n\n\n\n

In our group, thought\u2011provoking questions emerged:<\/p>\n\n\n\n

    \n
  • What is the real role of frameworks today, and what will it be in the future?<\/li>\n\n\n\n
  • Waterfall vs.<\/strong> Frameworks, or Waterfall +<\/strong> Frameworks?<\/li>\n\n\n\n
  • Will certified professionals really be necessary or make a difference?<\/li>\n\n\n\n
  • Follow the framework strictly, or adapt it to each team’s reality?<\/li>\n<\/ul>\n\n\n\n

    There were no easy answers \u2013 it truly was a wicked problem!<\/p>\n\n\n\n

    Heated discussion that converged<\/h2>\n\n\n\n

    The discussion was challenging because we were all very attached to our lived experiences, which made it harder to think “outside the box” and re-imagine things — which was the goal of the event after all!<\/p>\n\n\n\n

    We debated (a lot) about the use of frameworks: up to what point do they help, and when do they start to get in the way? <\/p>\n\n\n\n

    The conversation shifted to whether teams are truly Agile or still need someone (coach\/Scrum Master\/Manager) guiding them on how to work. <\/p>\n\n\n\n

    I\u2019ve noticed that many people believe they know Agile inside out. They\u2019ve practised it so often that it feels automatic. However, others in the group countered, \u201cThey think they know it, but for some reason they don\u2019t actually do it right — that\u2019s where the coach adds real value.” <\/p>\n\n\n\n

    Despite heated discussions, we finally converged: the way we use frameworks today is not the same as it was before, and it certainly won\u2019t be the same as how we will use them in the future. They are a great starting point for new teams seeking their own path, or a set of guidelines for more mature teams. But always consider the context, the current way of working, and more. Never impose them.<\/p>\n\n\n\n

    Takeaways: four counterpoints to revolutionise how you use frameworks<\/h2>\n\n\n\n

    We concluded our discussion with four bold counterpoints. A flip of the status quo to revolutionise how we use (or evolve) frameworks: <\/p>\n\n\n\n

    1. Guidelines OVER Frameworks<\/strong><\/p>\n\n\n\n

    The focus should be on guidelines rather than strict rules. Past experiences and knowledge can and should be used, but without becoming a limitation. Use them as a baseline, not as the rulebook that cannot be changed.<\/p>\n\n\n\n

    2. Pragmatic Solutions OVER Dogma<\/strong><\/p>\n\n\n\n

    Focus on pragmatic solutions: in the pure sense of the word, value what works in practise. This is directly connected to the empiricism of agility, not clinging to dogmas or beliefs. No more “just because it is in the book,” “it has always been like this,” or “it is a framework rule.”<\/p>\n\n\n\n

    Test, measure, adapt \u2013 pure Agile.<\/p>\n\n\n\n

    3. Co\u2011Creation OVER Enforcement<\/strong><\/p>\n\n\n\n

    As Agilists, prioritise co\u2011creating ways of working together with the team. There is no framework that fits everyone perfectly. It is necessary to work together and reach an ideal way of working for each team. Enforcement? No way!<\/p>\n\n\n\n

    4. Evolution OVER Stagnation<\/strong><\/p>\n\n\n\n

    We live in a rapidly changing world: work environments, companies, and tools are changing all the time. If everything else evolves, why should frameworks not evolve as well? Incorporate these new aspects and variables; do not stay stagnant. Frameworks have been useful, and still are useful in part, but they need to evolve. When frameworks stop evolving, they move from enabling agility to actively limiting it.<\/p>\n\n\n\n

    These are not just gimmicky catchphrases — they are the essence of the four hours of discussion together.<\/p>\n\n\n\n

    Edge of chaos: the remodeled future of frameworks<\/h2>\n\n\n\n

    Frameworks were an essential reference point, but today teams are crying out for tailor\u2011made models for their unique chaos. <\/p>\n\n\n\n

    Will frameworks die? That does not seem likely. They are still useful in certain ecosystems, but they call for remodelling and evolution to embrace today’s chaotic environment. <\/p>\n\n\n\n

    Our debate shed light on this: we came out seeing a future where frameworks will go through (or are already going through) an edge of chaos, a transition zone with controlled disorder until stability reemerges, birthing fresh frameworks, revamped old ones, or even a future without them altogether.<\/p>\n\n\n\n

    Time for action: My four commitments<\/h2>\n\n\n\n

    For now, as Agilists, our mission is to create environments where experimentation is free, adaptation is fast, and evolution happens without collapse, constantly seeking better ways of working that are tailored to each team. I\u2019ve decided to walk the talk. <\/p>\n\n\n\n

    Some of these actions I\u2019m already doing in my teams; others I\u2019m adding right now to shake off stagnation. Here\u2019s what I commit to: <\/p>\n\n\n\n

      \n
    • Question every single meeting with my teams: Does it make sense? Is it serving a purpose, or are we doing it just because the framework says so? And I’ll be bold to change it — cancel, shorten, or reinvent.<\/li>\n\n\n\n
    • I will experiment with practises from different areas, methodologies, books, and even frameworks, but always in my context. I\u2019ll see how they serve my purpose, ditching dogma for what actually works.<\/li>\n\n\n\n
    • I will meet my team where they are: observe their real struggles and co-create a coaching backlog together, tackling issues with agile practises that fit, nothing enforced or imposed.<\/li>\n\n\n\n
    • I will gather insights from experiments and tweak them to fit my reality. Nothing stagnates — always evolving how we work.<\/li>\n<\/ul>\n\n\n\n

      There you have it — my four commitments to put guidelines first and keep agility alive. <\/p>\n\n\n\n

      What about you? What\u2019s your bold move? What actions will you take to ensure your and your team\u2019s success isn\u2019t tied to implementing a framework? <\/p>\n\n\n\n

      Share it in the comments. Let\u2019s co-create the future of frameworks together — tag a teammate who needs this nudge!<\/p>\n","protected":false},"excerpt":{"rendered":"

      Remember when Scrum solved all of your team’s problems? At the first sign of trouble, you just went back to the Scrum Guide and found all the answers inside. And […]<\/p>\n","protected":false},"author":8142481,"featured_media":8104029,"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":[918,883],"tags":[],"content_source":[],"class_list":["post-8103977","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-framework","category-mindset"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/posts\/8103977","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\/8142481"}],"replies":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/comments?post=8103977"}],"version-history":[{"count":7,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/posts\/8103977\/revisions"}],"predecessor-version":[{"id":8104706,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/posts\/8103977\/revisions\/8104706"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/media\/8104029"}],"wp:attachment":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/media?parent=8103977"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/categories?post=8103977"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/tags?post=8103977"},{"taxonomy":"content_source","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/content_source?post=8103977"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}