chevron_left Back to insights

7 common Agile Transformation pitfalls and how to avoid (or fix) them



Reading time

2 minutes


Jeroen Nollet


These days, more and more companies are going through Agile transformations. The switch to Agile frameworks seems a necessity to keep on competing in today’s dynamic market environment. Therefore, organizations find solutions to go through this transformation as fast as possible and to avoid the most common Agile Transformation pitfalls.

Our Agile expert, Jeroen Nollet, dives into it and is happy to share his experiences.

I’ve been part of multiple Agile transformations as a Scrum Master during the past years and I often see the same problems returning. I’m happy to share them with you in a series of seven blog posts and hope you will be able to anticipate these problems and find alternative solutions to fix them.  

Jeroen Nollet

In a nutshell

For every problem (or pitfall, in this case), there is a solution. Let's highlight the most important conclusions below.

1. Big Bang Agile Transformation

Rome wasn’t build in a day, so your organization won’t be transformed all at once either. It might be tempting to do a big-bang rollout after a successful proof of concept, but try to resist. You will learn much more when you take a more gradual approach.

Read more

2. The 'one size fits all' approach

Your organization is unique and complex. Don’t try to fit every team into the same box and provide enough flexibility for them to determine their most efficient way of working.

Read more

3. Custom Agile frameworks

Don’t be tempted by consultants to create a custom framework. This beats the goal of an Agile Transformation. Why? Custom frameworks will be built on (some of) the existing processes you want to transform and therefore won’t cause any transformation.

Read more

4. Dependency management

Dependencies will quickly become bottlenecks while transforming your organization. Have an eye for common dependencies and think about how you can eliminate them to speed up your teams’ performance.

Read more

5. Output vs. outcome

Don’t focus on the output of individual teams to determine your successes. Instead, focus on how E2E (end to end) value is delivered to the end users.

Read more

6. Inspect & adapt your Agile Transformation progress

Agile Transformations are complex on all organizational levels. Because of this complexity, make sure to regularly look back to see what you learned on both team and company level and adapt accordingly.

Read more

7. Employee investment

Don’t forget your employees when you are in the middle of an Agile Transformation. Invest in relevant trainings so everyone knows what you are doing and why you're doing it.

Read more

More on Agile Transformation pitfalls?

Want to read more about these Agile Transformation pitfalls? Check out the full blogposts on our insights section by Jeroen Nollet!

about the author

Jeroen Nollet

Jeroen Nollet is Scrum Master and Agile Delivery Lead at The Value Hub. Certified as a Professional Scrum Master (level lll) and Professional Scrum Product Owner (level lll), he coaches teams in their Agile transformation challenges. By deeply examining team dynamics and designing practical solutions for specific problems, he helped out many customers in the scaling of their Agile workflow before. His technical background as a Java Developer turns out to be one of the biggest assets too in working with technical teams and issues.

Discover other insights