A Developer can be slow for many Reasons
wasted effort on unclear specifications
Lack of support (analysis,design,DB,technical environment)
attachment to a specific task that may block a procedure
incomplete design
unrealistic deadlines
requirements continue to change
unfamiliar technology or methodology
team members don't work efficiently
complicated and unfamiliar design
necessary functionality cannot be implemented (Blocking implementation issue)
using new technologies that developers need time to study
misleading information from technical documents
added late on a project
System Administration Issues that mislead
Bugs that are hard to re produce .
And many and Many
On the other side developer may not have the technical skills .
do you have a coordinator that analyzes the task performance on each meeting ?
are tasks all broken into smaller tasks so you can find where the problem starts ?
it takes more than just a Senior Developer to constitute a supported Team that works at a project . I have met many Senior Developers which have experienced this Issue
It is important to monitor the Tasks a Developer has two times a week and evaluate the performance on each task .
Some Senior Developers are defining aspects of the requirement Department and some not (i have seen Developers working as Analysts,Testers,QA and Doing coding all together).
what are his tasks?
check teamwork :
Even when you have a skilled motivated hard working developer a wrong team structure can eliminate all the efforts of a success (I have seem this) by reducing quality,damaging morale and slow down a project.
on a high performance team every person knows what to do and what is his role.
do you have mechanisms or methodology to know in which part the performance of each member is efficient and which is going slow or bad?
A good way is using tools like Jira and Monitoring tasks every 2–3 days (If you haven’t done that already ) ,if you don’t see improvement arrange a meeting and discuss with other team members the tasks that have not been accomplished , i remember a developer with very poor performance because the environment he was working was bad.
in Which Phase cycle are you in ?
what do you mean that code quality is just on par with other developers?
Does he have time enough to write quality Code ?
unreasonable schedule pressure can make very bad code even from the best Developers .
Like saying Supreme Static development in an oop Language.
Everything we hear is an opinion, not a fact. Everything we see is a perspective, not the truth.
**~ Marcus Aurelius, Roman emperor**
Level Expectation
Junior -> Can you help me to do this?
Mid -> Can i do like this?
Senior -> Do you have project for me to work ?
Staff Engineer -> Does our organization have any problems need to solve?