Hacker News new | ask | show | jobs
by arp242 660 days ago
I don't think it needs to be as "structural" as you're describing here. Simply "work on something else if you're stuck, come back to it after a day, two days, or longer" has long been one of my secrets to get stuff done.

I once worked somewhere that allowed you to work only on one ticket/task, before you were allowed to move on to another. Completely dumb policy for so many reasons.

2 comments

The one ticket only is how it is done at my current job (except in support, which is a whole new hell) and I hate how it actively deters me from using my brain (and time) efficiently.
My previous team's Scrum master kept bugging me because I had multiple tickets open most of the time. As if I were a child that could not manage his own tasks. I left as soon ia could.