What If An Agile Team Member Won’t Play Ball?

agile team member wont play ballWhat do you do if someone in your agile development team is simply not playing ball? Particularly if their behaviour is counter-productive to the key principles of agile development and is affecting the team’s performance.

One comment I’ve heard (not at my organisation by the way) was to apply the self-organised nature of Scrum and allow the team to raise the issues with the person directly and use peer pressure to make them feel uncomfortable in the hope they might leave. Admittedly in this case the person’s behaviour sounded particularly bad, but in any event this is not a good approach.

I’ve managed software development teams for many years (in the UK) and am currently responsible for a web development group of about 90 people. I think I’ve experienced every HR/management procedure in the book and keep promising to write a book about some of the more extreme examples (that are entertaining stories in hindsight but certainly weren’t at the time!).

To be honest, I found the idea of the team raising the issues as a group in the hope you wouldn’t need to fire him (presumably meaning he might jump) quite alarming.

Firstly, in UK employment law he’d potentially have a case for constructive dismissal if he knows his rights or gets good advice, and that carries quite a stiff penalty. Secondly there’s the issue of it not being appropriate to bully colleagues into leaving, even if they’re a complete pain in the backside!

I recently wrote a short blog post about an amazing statistic I heard; one consultancy firm suggesting you could lose 25% of your developers when moving to Agile Development.

The reality is that not everyone in your team will agree with the philosophies of agile development and some find it practically very difficult to adopt to the very dynamic nature of the process and the lack of clarity and certainty it can bring.

In my experience there’s only one way to deal with someone behaving badly in an Agile Development team (in fact in any team):

  • Any discussions must be 1:1 – air dirty laundry in private not in public
  • Explain that the person appears to be finding the Agile Development approach difficult or appears not to be on board
  • Outline why you think that’s the case, using constructive examples of how his behaviour is affecting his performance and the performance of the team
  • Tell him what good looks like; in the above examples, how could he have responded and what might the effect have been then
  • Try to understand why they’re behaving as they are; do they disagree with the principles, are they uncomfortable with the process, do they find group working difficult for some reason, or is something else bothering them? Remember bad behaviour is a symptom of something else
  • Adopt a supportive and understanding stance; don’t use personal or aggressive language; use non-emotive words such as “I feel”, “it’s perceived”
  • See if there is anything you or anyone else can do to help or support them better
  • If it’s a case of feeling uncomfortable with the principles and process, would training help
  • If not, perhaps regular 1:1 coaching sessions where you can discuss the day’s events and reflect on the situation outside of the main group
  • Remember he can’t control his capability but he can control his conduct. In the latter respect, insist that he does
  • It doesn’t matter how small, and however bad everything else is, catch him doing something right and praise him in public (be careful not to patronise, it must be sincere!)
  • If none of this works, consider whether there’s an alternative role that might suit him better – remember agile is not for everyone and some excellent people don’t get on with it. Remember the bad behaviours are a symptom not the cause
  • When you’ve exhausted all other possibilities and if the conduct issues persist, if you really are 100% committed to the agile approach, you may in the end have to resort to disciplinary action potentially leading to dismissal
  • If you have to take this path, make sure you consult your HR department and follow the appropriate process for your company and location

Finally, and just to reiterate, personally I love the agile development philosophy, but it’s not for everyone and not everyone can adapt easily to the change. Your first goal must be to change people’s behaviour through education and training, followed by some open 1:1 discussions with those reacting badly to the change or finding it difficult. First and foremost, try positive support and encouragement, even when it feels like it’s going against the grain.


See also: 10 Key Principles of Agile Development

2 Responses to “What If An Agile Team Member Won’t Play Ball?”

  1. Michael says:


    Great posting!

    You may also want to take a look at a blog entry I did last year on a similar topic — along with a cartoon too!


    - mike vizdos

  2. phloid domino says:

    The post failed to consider one possibility: what if the team member who “won’t play ball” is right?

    Shocking as it may sound, not every project and situation is a fit for Agile. And given the current level of hype about ‘Agile’, it’s entirely possible, even likely, that some projects will be mandated to “do Agile” by buzzword compliant managers.

    Don’t kid yourself, this happens all the time.

    Just maybe that recalcitrant team member has a point. Maybe this project is not a good Agile fit. Maybe the organization is not, or not supportive enough.

    Maybe that team member even understands Agile better than those who just get on the train because, well, just because.

Leave a Reply

What is 8 + 2 ?
Please leave these two fields as-is:
Please do this simple sum so I know you are human:)

There are 101 ways to approach anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”


“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”


“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”


“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”


“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”


“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”


“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”


“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”


“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”


“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”