I'm a manager of developers (and a developer myself), and I always prided myself on getting the most out of my team.<p>We've had a number of people join, and the team has changed a bit in the last year. In the last few months our velocity has really dropped and I don't know how to get people working faster again.<p>I look at the closed tickets and there just aren't that many. They're all really capable devs but the throughput is really low.<p>What questions should I be asking myself? How can I help unblock my team? Should I be leading by example and cranking out ticket after ticket, to show them how it's done?
I think the first thing you should start with is to understand if there is less productivity or not, and then understanding why.<p>Can you see that the tickets closed are less during a similar time period last year? Does the same pattern follow all old developers, or is it the new ones that don't have the same productivity? Are the tickets actually equal as last year, or has complexity increased and therefore decreased speed?
If there is a general decrease in productivity across the team including the senior developers, and you don't see any specific reason, then I would suggest talkin to the senior developers, highlighting what you see and start asking their opinions on it, what do they see have changed.
So as bullets<p>1. Try finding out the reason why before taking action (and find out if there is an actual decrease). And trying find where the issue lie is it with individual or team, with skill or motivation, external changes or internal processes.<p>2. If you cant find the answers, start talking to the teams most senior developers
What is your team delivering, for customers? It's not tickets and story points.<p>This recent article seems like what you need: <a href="https://newsletter.pragmaticengineer.com/p/measuring-developer-productivity-part-2" rel="nofollow noreferrer">https://newsletter.pragmaticengineer.com/p/measuring-develop...</a>