New answers tagged

2

There are already several good answers mentioning use of tools like PIP, peer review, and TDD, but I’ll mention one thing that strikes me. In your question you state I have a person in my team with average experience that always do the task exactly as requested as output but with low quality. But if he did it exactly as requested, you wouldn’t be asking ...


1

There have already been good answers to this question, but you may also want to consider using a test driven development (TDD) approach. For example, have the developer first write automated tests that validate the acceptance criteria on the user story. Only once those tests are written do they proceed to the implementation. This approach has several ...


0

There are a lot of drivers that can cause or contribute to an individual's performance, one of them being that he can be simply a low performer intrinsically. Once you have ruled out the various external drivers to performance as the cause or contributor to his performance, than focus on his tasks with measurable expectations and use a formal Performance ...


2

Since you added the Agile tag, I will answer from that perspective. In Extreme Programming (with "peer programming") and some implementations of Scrum or Kanban, teams will require a quality sign-off from a peer on the team before the requirement or "user story" can be considered for final acceptance. This puts what I call "positive peer pressure" to work, ...


Top 50 recent answers are included