We discussed rethinking estimation sessions back in planning for the processes revamp epic (BB-10142), but this wasn’t high enough in the priority list to make it for the first iteration.
However, I’ve found that in Bebop, we’re still not using the estimation sessions.
In the last 6 sprints, we’ve averaged 1.3 participants in the estimations sessions. This isn’t enough to make these estimation sessions worth it - eg. last sprint the story points set based on the session are simply my guesses.
The other cells have not been using estimation sessions for a long time now.
In light of this, I propose dropping the estimation sessions from next sprint. In future we can incrementally refine how we manage story points in our docs.
If anyone has anything against this plan, please voice your concerns below before March 3.
I opened a PR to the handbook at opencraft/documentation/public!658 to remove this from our processes; please take a look if you’re interested or have concerns.
I also deactivated the checklist items in the Listaflow sprint checklist template regarding estimation sessions.
@tikr or @braden do you know how the estimation sessions automation in jira works? Could you help me disable it so no new sessions are created? Thanks.
I believe we can drop the part about moving out injections - there were some comments about that being annoying. But that can be a discussion for another day.
