Hacker News new | ask | show | jobs
by fpdavis 1437 days ago
I have had similar employees and sometimes they just aren't a good fit. But first, are you following all of the Scrum/Agile methodologies? Are you doing DAILY STAND UPS so the TEAM can help hold individuals accountable? Are you performing RETROSPECTIVES at the end of each SPRINT... you are doing short sprints right :) Is the team making the assignments (as they should) or are you? Also, get away from estimating in days and go with generic units, the Fibonacci Sequence would be my suggestion. Make sure the team is defining the tasks and voting on the effort required for each task. I would do this for a couple of months to let the team get into a flow and begin to learn how to estimate things. Then observer how your problem employee votes to see if they are particularly high or low and see how many tasks they complete compared to the rest of the team.

If after all of that there is still a problem, setup an End-of-Day meeting each day with the individual to go over what they accomplished that day... actually having them show you code, interface, documentation, something that they had accomplished that day. In collaboration with the employee setup reasonable expectations and goals that you (hopefully) can both agree on. If the goals are not met, write them up, rinse and repeat. After a couple of write ups suggest that they are not a good fit and should think about moving on, after three or so you should let them go.