https://www.dtsato.com/blog/2008/08/26/agile-2008-estimating-considered-wasteful-introducing-micro-releases/ We can change! Wed, 07 May 2014 20:15:42 +0000 hourly 1 https://wordpress.org/?v=4.2.39 https://www.dtsato.com/blog/2008/08/26/agile-2008-estimating-considered-wasteful-introducing-micro-releases/comment-page-1/#comment-1872 Mon, 10 Nov 2008 18:07:24 +0000 http://www.dtsato.com/blog/?p=139#comment-1872 You can adapt the approach to your needs, but the whole idea is that you don’t have 3-6 months release cycles, but they ideally take less than a week (yes, less than an iteration). If you still want the long-term vision (3-6 months) you can do whatever is not-wasteful, but you still need to acknowledge that it’s still a guesstimate. It’s a different approach and I wouldn’t recommend it to anyone who is still not used to the short cycles of an Agile approach and, as I said, this approach requires a very close collaboration with the customer.

]]> https://www.dtsato.com/blog/2008/08/26/agile-2008-estimating-considered-wasteful-introducing-micro-releases/comment-page-1/#comment-1871 Mon, 10 Nov 2008 17:46:15 +0000 http://www.dtsato.com/blog/?p=139#comment-1871 The problem I see with this is that estimation is usually used to estimate the completion date of a Release, say a 3-6 month long release, which is too difficult to do on a gut-feel. Maybe the features should have estimation but the stories within them should not?

]]>