How would you deal with a team that resist the Agile methodology?
Welcome to part 5 in our agile coach interview questions series, where John McFadyen answers common questions asked of agile coaches during interviews and client engagements.
Deal with is a strong word. We aren’t there to enforce a specific way of working; we are there to invite the team to explore opportunities and discover for themselves which way of working best suits the team, the environment, and the unique challenges they are trying to overcome.
Understand the team
Your first objective is to understand what the team are resisting.
When we talk to teams, we often discover that they have had a specific methodology or agile framework imposed on them. Something they have little to no understanding of, and so their resistance comes from a lack of understanding and experience with the framework.
Sometimes, they have tried scrum or Kanban, or some other form of agile framework, and it has backfired on them. It is very seldom that the framework failed; you discover that the things they were doing and what was being imposed on them wasn’t scrum.
It was some variation of it, packed with duties, tasks and unnecessary documentation, that prevented the team from doing great work.
Fair enough, if I had to deal with that, I also wouldn’t be a fan of ‘scrum’.
Remember, you are dealing with smart, creative, and committed individuals who want to be great at their job. If they are resisting something, it is likely because they have valid and good reasons for it.
Uncover what those reasons are, interrogate their experience, and gather as much information and data as possible to understand the team environment.
9 out of 10 times, you will discover that what they tried before wasn’t anything like scrum or agile. You will discover that resentment built because they didn’t understand the purpose of the change imposed on them, and very little agreement was achieved when implementing the new ‘solution’.
Co-Create a way forward
You want to have conversations with the team that help them understand what problems and challenges they face, and how best to overcome those problems.
You want to explore what is happening in the team environment, why it happens that way, and how that all came to be. The systems, the processes, the whole way of working.
Once the team are having those conversations with the aim of continuous improvement, you find that resistance melts away. We’re exploring how things work, how we would like them to work, and what the benefits of solving these problems will be.
There is nothing to resist.
I would offer insights from my experiences with other teams, and I would invite each member of the team to add their own insights, ideas, and experiences into the mix.
We want everyone on the team to be committed to co-creating new processes, systems, events, and ideas that will help the team achieve their goals. We want a solid contribution from everyone on the team to ensure that we have buy-in and agreement on the way forward.
A way forward that works for the team solves the problems that exist and helps the team create products and features that truly delight customers.
Effectively, consistently, and continuously.
If the team choose some aspects of scrum or Kanban or whatever framework they want to go with, that’s great. If they choose to remove certain elements, that’s great too.
The only requirement you have of the team is that transparency, inspection, and adaptation are baked into the style of working as a rock-solid foundation for product development.
It doesn’t matter where we start, it simply matters that we do start and build on the idea of continuous improvement.
Understand what challenges the team face and work with them to overcome those challenges whilst continuously improving processes, tools, systems, and any other element that will ensure progression and evolution.
When the team owns the new working style and understands why they have co-created this new approach, they actively want to see it succeed. They actively want to contribute and do a great job because it’s designed by them, for them.
That would be my recommendation for dealing with a team who resist Agile frameworks and styles of working.
If you are interested in becoming an agile coach and value mentored, coach-driven skills development in your journey to mastery, visit our Growing Scrum Masters website.
For more information on John McFadyen, connect with John on LinkedIn at https://www.linkedin.com/in/johnmcfadyen/.
If you like the idea of becoming a scrum master and want to achieve internationally recognised and certified accreditation as a scrum master, visit our Certified Scrum Master (CSM) course page.
If you are already a scrum master and want to upskill to a more advanced level of knowledge and agile coaching capability, visit our Advanced Certified Scrum Master (A-CSM) course page.
If you have several years’ experience as a scrum master and want to validate and certify your professional skills, visit our Certified Scrum Professional Scrum Master (CSP-SM) course page.
#agile #agilecoach #agilecoaching #agileprojectmanagement #agileproductdevelopment #agility #businessagility #scrum #scrummaster #scrumtraining #scrumcertification #scrumalliance #agilecentre #johnmcfadyen #coach #coaching #certifiedscrummaster