At the beginning I had difficulty getting much done, but by the end it only took me about a minute to get into the zone. I think the other main problem I had (which culminated in me not continuing) is maintaining a regular schedule. 1 pomodoro a day doesn't seem that hard to do, but sustaining the pace over the long term was pretty difficult. I ended up skipping lots of days (sometimes going a week between pomodoros) and finally gave up. One of these days I'll learn how to overcome that problem :-)
Having it work related would mean that sheduling would be easier. I would try to do that for first half hour of the day. If that really does improve the 'getting into the zone' so much, that would really be awesome.
My original goal was to practice constant refactoring on a non-toy sized problem. Normal katas necessarily require you to work on toy problems. Because of this many interesting real world problems never come up. Frequently you can see people using techniques that aren't sustainable, for instance.
In the end, while I did get some value from that, by far the most interesting thing I discovered was that you can write code 1 pomodoro a day! If you take this as being about 1 weeks worth of work, I think my productivity is a bit lower than normal. However, it's not off by that much.
Even more interestingly, because I work in a timezone 9 hours separated from my colleagues I've always wanted to be able to hand over work. In other words, 2 people working on the same story. 1 person works during the night and the other person works during the day. They hand over the code in the morning and the evening. Using the TODO list techniques I was using in the kata (and making sure to end the day on a failing test), I've actually been able to accomplish this with like minded colleagues. It's actually quite incredible. Probably I should write a blog post about it ;-)
I would definitely be very interested in this. Seems like a smart way to work remote or on personal projects.
As if there was some weird rule stating "if you can't complete a thing in 15 mins, it will take you at least an hour"
For harder work, I need 3 hours and quiet. 4 hours seem to be the most efficient time chunk anyway, and after that it starts sharply falling (usually there is little difference if I work for 6 or 10 hours straight)