I commented on Scrum is hard to adopt and disruptive to your organisation before and I think that for most companies this is just beyond their comprehension. They are fundamentally misunderstanding agile and trying to do agile rather than be agile.
There are no trainings or certifications or even processes that can provide you with that understanding There is nothing but deep organisational change and hard work that can create that lean-agile way of doing thins that provides many companies with so much value.
If you want to be agile you will need to embrace:
- giving up management command-and-control
- going and seeing what the problems are rather than looking at endless reports
- encouraging and supporting people to serve as hands-on-master programmers for 15+ years
- close engagement between the hands-on developers and customers, without intermediates
- managers and architect who are pair-programming coaches
- real transparency – of delays, what’s wrong each day, …
- The candour to say “we don’t know”
- stopping sequential lifecycle practices and mind-set
- empirical process control
- replacing cube farms with team rooms and visual management
I do not believe that is it possible to sell a company agile, they must come to the realisation of what it entails themselves. Oh, you can introduce them to many of the practices and encourage them to experiment. You can teach individuals TDD and other test first methods but all you are doing is priming the pan and creating an environment where that spark of agility can smoulder. Then they will come to you.
I was recently contacted by a customer that I have worked with before to help them become more…well.. agile. They feel that they have a good understanding of the mechanics of Scrum and they they are gaining value at the team level, but they want more. They want to realise the greater organisational reality of agility and not just follow the rules.
In short they want to Build people, then products.
There are a great many thing that we can look at but until I can ‘go see’ how folks are working there is no way I can have any idea of a plan. I can however imply that there are some things that while not constants are good bets to look at and for:
- discourage ‘fake agile’ – the first thing to look at is if they really do have just the mechanics down or if they are starting to be agile
- encourage ‘Communities of Practice (CoP)’ – Sometimes referred to as guilds these CoP allow and encourage folks interested in a practice to collaborate regardless of the affinity they have to a particular discipline.
- encourage ‘go see’ – Encouraging managers to go to where the work is boing done will be immensely more valuable than looking at reports
If we can get some amount of time onsite to investigate and work on some of these things then that would make me happy. I am really looking forward to seeing how they have been getting on and how many of the issues we identified in the last engagement have changed.
Here is looking forward to future collaboration and experimentation.
Smart Classifications
Each classification [Concepts, Categories, & Tags] was assigned using AI-powered semantic analysis and scored across relevance, depth, and alignment. Final decisions? Still human. Always traceable. Hover to see how it applies.
What to read next
Empowering Development Teams: Cultivating an Agile Mindset for Lasting Quality
Explores how leaders can foster an agile mindset in development teams by promoting autonomy, mastery, purpose, and a culture of quality and …
Unmasking Agile: How to Spot Genuine Practices Amidst the Myths
Learn how to identify authentic agile practices, spot common myths, and understand cultural barriers that hinder true agility in modern …
Professional Scrum is for everyone in your organisation
Explains how involving everyone in Professional Scrum training fosters organisational agility, breaks down silos, and empowers teams to …
Beyond the Agile Illusion: Embracing True Agility in a World of Taylorism
Explores the difference between true agility and superficial agile practices, highlighting the impact of Taylorism and offering steps to …
Scrum is hard to adopt and disruptive to your organisation
Explains why adopting Scrum is challenging and disruptive, highlighting the need for training, mentoring, and dedication for successful …
Navigating Agile Transformation: Empowering Teams for Success in a Rapidly Changing Landscape
Explores effective Agile transformation by empowering teams, improving collaboration, focusing on value delivery, and fostering continuous …
Detecting agile theatre with real delivery signals
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Getting Started with Objectives & Key Results
Learn how to successfully implement OKRs by aligning clear strategy, fostering transparency, empowering teams, focusing on outcomes, and …
Futureproof Leadership: How CTOs Can Cut Through the Noise and Lead with Clarity, Confidence, and Culture
Struggling with tech change? Discover how clarity, evidence, and culture can futureproof your team, no chasing trends, just smart …
From Burnout to Breakthrough: How CTOs Can Lead with Clarity, Resilience, and Real Innovation
Feeling overwhelmed as a tech leader? Discover how to shift from chaos to clarity and build resilient, future-ready teams, without burning …
Human and AI Agency in Adaptive Systems: Strategy Before Optimisation
Explores the distinct roles of human and AI agency in adaptive systems, emphasising human-led strategy and accountability versus AI-driven …
Stop Chasing Trends: How Real Agility and DevOps Build Resilient, Adaptable Teams
Stop chasing trends, build real agility. Discover how DevOps and agile create resilient teams, smoother delivery, and sustainable …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
Why Big Bang Rewrites Fail: How Sustainable Change and Engineering Excellence Transform Legacy Systems
Ditch the Big Bang rewrite. Discover why sustainable, in-place change drives true engineering excellence and lasting transformation in your …
Is Agile Really Just a Mindset?
Explores Agile as a disciplined system of delivery, emphasizing engineering excellence, CI/CD, observability, and system design over mindset …
Telling People What to Do Is Not Leadership. It’s a Failure of System Design
Explores why real leadership means designing systems that enable team autonomy, flow, and accountability, rather than relying on …
From Legacy Pain to Modern DevOps: My Proven Roadmap for Real Engineering Transformation
Transform legacy engineering with a proven, step-by-step approach, learn how to automate, adapt, and build a resilient, modern DevOps …
The Definition of Done is a Commitment to Quality
Defines the Definition of Done in Scrum as a clear, shared standard for quality, ensuring increments are releasable, transparent, and …
Why Your Definition of “Done” Is Holding Back Quality, Agility, and Trust, And How to Raise the Bar
Is your team’s “done” really done? Discover how a clear, objective definition of done boosts quality, agility, and trust in product …
Acceptance Criteria vs Definition of Done: Why Getting This Right Builds Trust and Delivers Quality Faster
Stop confusing acceptance criteria with definition of done, learn the crucial difference to boost quality, speed, and trust in your agile …
How to Evolve Your Definition of Done: Start Small, Grow Smarter, and Build Lasting Momentum
Unlock a smarter Definition of Done, start small, evolve standards, and build team momentum without overwhelm. Discover how progress drives …
Why Most Transformations Fail Without Honest Conversations
Most transformations fail without open, honest conversations that address real issues, making transparency and tough dialogue essential for …
Why Your Definition of Done Is the Secret Weapon for Real Business Impact and Agile Growth
Transform your definition of done into a strategic advantage, deliver real value, reduce risk, and drive business impact with every sprint.