Similar to the method in this article, I had already applied it to development. I used to work on each tickets one by one, move on when it's fully done but thi

Similar to the method in this article, I had already applied it to development. I used to work on each tickets one by one, move on when it's fully done but this got very tiring, sometimes I would have to come back to a bug because it was related to another one. I started to work on each ticket for 15~30min max, moving on regardless of whether I had got anything done. When I started to feel the burn from a ticket I would skip it and move on to the next ticket. What I found was that I ended up getting far more done in less time. What happened was kind of like skipping a question on a test and coming back to it later. Your brain keeps working on it, or maybe you had to ask stackoverflow and it took time for someone to answer it. Anyways, time automatically began working for me, instead of me trying to bang my head against the keyboard until one thing was completely finished. Once you shake off the feeling of unproductivity and begin seeing just how easy things are when you work on multiple tickets in short time intervals, its far worth the effort. I've yet to name this technique, I shall call it 'notastartups maximum ticket resolve method'