Small but important lesson today – think about who’s gonna work on a ticket, not just how much work is required.
I had shortlisted and prepared a good set of tickets for the next release: not too many story points with good business value. We usually go through these in a planning meeting, but one of the devs had a quick look today and pointed out something I had glossed over. Many of the tickets were focused on improving a particular feature – which made it more difficult to split and distribute the work between developers.
Worst case scenario? What could have happened is that one developer would be working on these tickets, while the other would be doing nothing. Good thing we have devs who take initiative to point these out.
So, think about who, not just how much.