Comments on: Projecting into the Future http://blog.gdinwiddie.com/2010/04/22/projecting-into-the-future/ Effective software development Wed, 08 Feb 2012 21:01:40 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: George Dinwiddie’s blog » Iteration, Increments, and Timeboxes http://blog.gdinwiddie.com/2010/04/22/projecting-into-the-future/comment-page-1/#comment-120847 George Dinwiddie’s blog » Iteration, Increments, and Timeboxes Tue, 08 Mar 2011 17:46:52 +0000 http://blog.gdinwiddie.com/?p=426#comment-120847 [...] that, all things being equal, future timeboxes will be about as productive as past ones, making estimates into the future reasonably accurate without undue [...] [...] that, all things being equal, future timeboxes will be about as productive as past ones, making estimates into the future reasonably accurate without undue [...]

]]> By: George Dinwiddie’s blog » The Importance of Detailed Planning http://blog.gdinwiddie.com/2010/04/22/projecting-into-the-future/comment-page-1/#comment-105876 George Dinwiddie’s blog » The Importance of Detailed Planning Thu, 13 May 2010 17:38:46 +0000 http://blog.gdinwiddie.com/?p=426#comment-105876 [...] chart is way too much work to keep up to date with such volatile and detailed data.  I suggest using a burn-up chart, instead.  Developer tasks is way too detailed a view for senior management.  Steering the [...] [...] chart is way too much work to keep up to date with such volatile and detailed data.  I suggest using a burn-up chart, instead.  Developer tasks is way too detailed a view for senior management.  Steering the [...]

]]> By: D. André Dhondt http://blog.gdinwiddie.com/2010/04/22/projecting-into-the-future/comment-page-1/#comment-105251 D. André Dhondt Fri, 23 Apr 2010 07:03:11 +0000 http://blog.gdinwiddie.com/?p=426#comment-105251 George, Are your teams getting paying-customer feedback more often than once every 4 weeks? For milestone, coarse-grained planning, we've stopped doing t-shirt size estimates. Instead we work on finding a scope that can fit inside a business-determined investment into a particular functionality. See more at http://dhondtsayitsagile.blogspot.com/2010/04/fan-out-release-planning.html George,

Are your teams getting paying-customer feedback more often than once every 4 weeks? For milestone, coarse-grained planning, we’ve stopped doing t-shirt size estimates. Instead we work on finding a scope that can fit inside a business-determined investment into a particular functionality. See more at http://dhondtsayitsagile.blogspot.com/2010/04/fan-out-release-planning.html

]]>