Follow up question from here:
One of my developers is having trouble estimating his work. For the past few weeks he has committed to work, and once stuck in is not able to complete it. Burn down charts then goes out of whack.
My other developer in the team is also concerned that he is not performing.
Approaches I have taken so far:
- Using daily stand ups to deal with the impediment. I have been giving the slow developer tips; get the easy tasks out of the way then do the hard ones.
I have even explicitly asked him on 2 -3 occasions if he will complete the task in time. His attitude has been 'yeah I will do', but then on the day tell me he can't complete it.
- I have asked the developer if he needs the other resource to step in and help him. He would always say no.
I am now starting to run out of ideas on how to deal with the slow developer. I am starting to think that he does not care about respecting the burn down charts, and is carrying the attitude that it will be done, when it is done.
I am encouraging the team to become more cross functional. In this instance that would not have helped anyway, because the task in question has to be completed by the person who started it. Otherwise we will have too many cooks spoiling the broth.
I have also educated the developer about the business objectives, and the team velocity is what is being tracked etc Developers agree that this is the right way to deliver work, fast developer is thriving, slow one isn't.