Personally as sprint planning manager I do not find them useful: the semantics are not clear, they’re a weak signal of ticket readiness anyway, they get outdated very quickly, and they’re ignored (if we want a ticket in the sprint, we put a ticket in the sprint, regardless of a little planning label).
Also, in looking for the source again, I only find this reference: “Ensure tickets ready to be pulled into a sprint are properly marked and ranked higher in the backlog.” in the handbook. And this is a hard thing to do; probably better to simply leave all this up to the relevant epic owners, who know better the budgets, ticket scopes, scheduling, etc.
I’d propose deleting these “Not ready to pull in” and “Ready to pull in” labels if no-one finds them useful.
While not fulfilling the original intent, I always found “Ready to pull in” useful when doing sprint planning chores as a marker for tickets I had already verified as having a complete description and acceptance criteria.
Thanks for your responses. Due to the general consensus that these are not useful, I’m going to go ahead and delete these labels to reduce noise in Jira. (I’ll delete the labels altogether if I can, otherwise simply remove them from the tickets in the backlog and stop using them.)
@paulo perhaps we can move toward a new method for marking tickets that have been verified in the future. For now, I don’t think we have a good process for this, as I believe regardless of the “ready/not ready” status, epic owners schedule tickets as they desire.
Ok, it doesn’t look like I can delete them. They can be found on the Releases page in Jira, but they are read-only for me. Maybe @braden can delete the “Not ready to pull in” and “Ready to pull in” releases?
For now, I’ll just remove them from tickets and stop using them.
A little late to this party, but one more reason in favor of removing those labels is that they become irrelevant once tickets that have them are added to the current sprint (and they become visual clutter on the backlog view).
–
I removed the remaining tickets from Ready to pull in (67 tickets) and Not ready to pull in (5 tickets); they were all done or archived. Then I went ahead and deleted these versions
I’ll work on updating docs relating to sprint planning where I can too. Although, I don’t think I have access to listaflow admin for updating the relevant checklist; could someone promote my account and link me to the admin url please? cc @Fox
Due to the general consensus that these are not useful, I’m going to go ahead and delete these labels to reduce noise in Jira. (I’ll delete the labels altogether if I can, otherwise simply remove them from the tickets in the backlog and stop using them.)