{"id":19345,"date":"2025-07-07T14:59:03","date_gmt":"2025-07-07T12:59:03","guid":{"rendered":"https:\/\/scrumacademy.nl\/blog\/zit-agile-in-de-storming-fase-een-overpeinzing-en-oproep-van-gert-jan-danenberg\/"},"modified":"2025-07-07T14:59:12","modified_gmt":"2025-07-07T12:59:12","slug":"zit-agile-in-de-storming-fase-een-overpeinzing-en-oproep-van-gert-jan-danenberg","status":"publish","type":"post","link":"https:\/\/scrumacademy.nl\/en\/blog\/zit-agile-in-de-storming-fase-een-overpeinzing-en-oproep-van-gert-jan-danenberg\/","title":{"rendered":"Status of Agile? A reflection and call by Gert-Jan Danenberg."},"content":{"rendered":"\n

<\/p>\n\n

This year I have regularly asked myself the question, “Has Agile brought what it promised?” The honest answer? Not quite. It seems that speed was sometimes considered more important than value, and mechanical Scrumming gained ground on really good teamwork. The one-size-fits-all approach shifted the focus away from custom solutions, which are precisely what is needed for teams and organizations to truly thrive. And yes, that’s when things start to squeak and creak. That’s when you get stuck. But is that a reason to jettison Agile? Absolutely not. <\/strong><\/span><\/p>\n\n

Not only is the storm raging outside, but in Agile work we will see quite a few storms pass by in 2024. In short, we might just be in a storm phase. This is the time when everything stops running smoothly for a while. The new patterns are challenged, teams get frustrated faster, and there is a natural urge to revert to the old, familiar. It feels tempting: “We used to do pretty well, didn’t we? But let’s face it, you started this journey, this change, for a reason. The old didn’t work anymore. That’s why you chose Agile. <\/p>\n\n

Every transformation, whether at the team level or across the organization, has such a difficult moment. It is similar to the “storming” phase in Tuckman’s model of team development. This is where the real work begins: you break through old habits, make yourself vulnerable and learn to work together in a new way. That process is painful, but essential. And this is precisely when Scrum Masters<\/a>, Product Owners and Managers must take their roles to help teams reach the next level. <\/p>\n\n

Status of Agile: Not backward, but full steam ahead<\/strong><\/strong><\/h3>\n\n

Okay, before we can bang ahead, still, let’s go back to why you ever started with Agile. What did you want to achieve? You wanted: <\/p>\n\n

    \n
  1. Faster to market with products and services<\/li>\n\n\n\n
  2. Focus on customer value<\/a> by delivering only what really matters<\/li>\n\n\n\n
  3. Cutting waste by working together more efficiently<\/li>\n\n\n\n
  4. Getting the best out of yourself and your team because you knew there was more to it<\/li>\n<\/ol>\n\n

    And then? Your start with Agile working gave energy. Everyone felt the drive to move together: faster, smarter and with more impact. But after that initial boost comes the staler period, which always comes. The peaks get lower and enthusiasm threatens to ebb away a bit. Let this be exactly the time when personal leadership<\/a> is desperately needed. Not to return to the old, but to ride out the storm. Full speed ahead. <\/p>\n\n

    What is your next level?<\/strong><\/strong><\/h3>\n\n

    But what do you need to move forward in this stormy phase? The key lies in the roles within Agile<\/a>. The Scrum Master is more than a facilitator; it is a Change Agent who leads teams through this phase. The Product Owner is not just a backlog manager<\/a>, but a strategist who continues to prioritize customer value. And the Manager is more than a supervisor; it is an inspirer who gives teams confidence and creates space for growth. My call to you is simple: find the depth. Get the wheels turning again. Give teams the tools and confidence to move forward. Ask questions like: <\/p>\n\n