I just want to piont out, that’s a general guideline about time tracking. But for estimation session, I very distinctly remember the directive “log the time spent on estimating the ticket on the ticket itself” (paraphrased). I spent some time trying to identify this in the handbook and but couldn’t. But I can swear this was there somewhere. Maybe someone else has a better idea of where this is. What @maxim is pointing out is a real pain point.
I would agree that it has the potential value of providing all that, but I don’t think it does in practice. Everyone will in any case go through all the tickets when assigning themselves work, which is when they can do most of the above. I often go through tickets I find interesting, even if they are assigned, but if a ticket is assigned and has a reviewer, we can assume that most issues that need to be caught are already caught.
I think it was @maxim who made a pretty good suggestion in a meeting once about not just giving points, but also explaining why you give those points so the final estimation can take that into account. I did this a few times, and I get the value of it, but if we have to come up with a new process I think we can consolidate things.
1 Like
Yeah true true. Maybe I’m thinking from a more idealistic point of view.
I’m wondering if there is still room for a semi-formal process for everyone to look at all the tickets before a sprint, even ones that are assigned and ready. I believe this can be valuable for extra insight, drive-by thoughts, etc. Maybe some recently did something similar and can share tips. Those last minute checks from extra eyes. 