Supporting a Struggling Developer in a Scrum Team

How I Tried to Support a Struggling Developer in a Scrum Team

Every Scrum team has its ups and downs when it comes to productivity. Some developers are super consistent, while others struggle to keep up. I had one team member who was always engaged during planning and retros but, when it came to daily huddles, he’d just say everything was ‘on track’ with no blockers. But then, right before the sprint review, his tasks weren’t done. If his work was critical, it messed up the release schedule. If it wasn’t, his half-finished code would likely never see the light of day.

What I Did to Help

Instead of jumping to conclusions or comparing him to others, I decided to take a structured approach and actually support him. Here’s how I tackled it:

1. Looked at His Story Points

   • I tracked how many story points he completed over a few sprints and made some charts to see if there was a real pattern.
   • The goal wasn’t to compare him to others—just to see if he was consistently struggling.

2. Set Clear Expectations

   • At the start of each sprint, I got him to commit to specific tasks.
   • This way, he knew exactly what was expected, and there was no room for vague updates.

3. Checked In During Daily Huddles

   • Instead of accepting a generic ‘everything’s fine’ update, I took a look at his tasks and Git branches.
   • This helped confirm that he really wasn’t facing issues, or if he was just hesitant to bring them up.

4. Had Weekly One-on-Ones

   • I set up casual weekly check-ins where we could talk about work and anything else on his mind.
   • This gave him a space to open up about challenges he might not feel comfortable sharing with the whole team.

The Outcome

After a few sprints, things started improving. His completed story points went up, and he was more upfront about his progress and blockers. It turned out that a mix of structure, support, and accountability was what he needed to get back on track.

Takeaways

• Track Progress Over Time: Looking at sprint data helps spot trends without unfair comparisons.
• Set Clear Goals: Having clear commitments upfront keeps things on track.
• Verify Progress Daily: Don’t just take ‘it’s fine’ at face value—check the actual work.
• Provide Personal Support: One-on-ones can reveal hidden struggles and make a big difference.

In the end, it wasn’t about micromanaging but rather creating a space where he felt supported and accountable. However, if you think I would say something like if you’re dealing with a similar situation, try these steps—they worked for me, and they might work for you too! , you are wrong. Because this dude asked me for his improvement data to apply for a better-paid job. So, scrum master plays critical role in a team, but so does the money 🥲🥲🥲