26 Apr '13, 9pm
@gdinwiddie BTW: others also describe @arlobelshee Naked Planning with "no estimation":
I just got the chance to listen to this interview with Arlo Belshee about Naked Planning (”Kanban Simplified”): http://cdn2.libsyn.com/agiletoolkit/Agile2008_Arlo_Belshee.mp3 Highly recommended. My summary of Naked Planning: Teams work toward delivering Minimum Marketable Features – usually chunkier than User Stories but more relevant to customers. Think “administrator can set user permissions” vs what you might break that down to in terms of finer-grained stories. The dev team breaks MMFs into tasks as appropriate. Teams work on MMFs in a ratio of about one MMF to every two pairs. There is no estimation (it’s usually wrong, there’s no particular reason why the time before you start a story – when you know very little – ought to be when you assess cost). Instead a pure yesterday’s weather approach is taken: you write down the date you start the MMF, and the date you finish...