By popular demand (OK it was only one person who asked, but I am sure he is very popular), this post will cover our experience at Huddle on what makes an appropriate maximum story size for it to be planned in an iteration or sprint. Again this is a much asked, and much answered question, and this is not the right answer - just the answer that has worked for us (and a few that did not work along the way).
I was disturbed recently to hear that a major internet company is planning to move their entire QA operation to India. I’m not against offshore development done right (I have seen in done well, badly and terribly in my time), but this is not about offshore development: the development team remain firmly in London. This is a change to QA from being on the other side of the building from development (bad enough) to a continent and several time zones away. This is craziness, especially for a company trying to embrace agile software development.
The uptime of a site like Huddle.net is of vitally important, so I was pleased to see that recent performance hit 99.99% - four nines. See my recent post on the Huddle blog for more details.