Comments on: Naked Planning Explained – Kanban in the Small http://aaron.sanders.name/agile/naked-planning-explained-kanban-in-the-small it's almost certain! Fri, 22 Jan 2010 02:54:56 -0800 http://wordpress.org/?v=2.9.2 hourly 1 By: Is estimation waste? « Quality Software Development with Ease http://aaron.sanders.name/agile/naked-planning-explained-kanban-in-the-small/comment-page-1#comment-571 Is estimation waste? « Quality Software Development with Ease Thu, 07 Jan 2010 04:45:15 +0000 http://aaron.sanders.name/kanban/naked-planning-explained-kanban-in-the-small#comment-571 [...] is what I gathered from the above mentioned screencast, Arlo’s comment on this blog entry by Aaron Sanders explaining Naked Planning, this podcast from Agile 2008 and this short video from Agile 2007. I don’t think there is [...] [...] is what I gathered from the above mentioned screencast, Arlo’s comment on this blog entry by Aaron Sanders explaining Naked Planning, this podcast from Agile 2008 and this short video from Agile 2007. I don’t think there is [...]

]]> By: SasHo http://aaron.sanders.name/agile/naked-planning-explained-kanban-in-the-small/comment-page-1#comment-338 SasHo Tue, 25 Aug 2009 22:18:08 +0000 http://aaron.sanders.name/kanban/naked-planning-explained-kanban-in-the-small#comment-338 Sounds interesting. I can see how this can work on a scope based project. What about time based projects? Simply imagine, that a customer calls and wants a new 'take me to mars' functionality, then wants to know how much will it cost and when can it be delivered, because time is of the essence. We have never implemented a feature of such complexity (...and most probably never will), therefore I don't have a clue on the effort needed. What am I to say? Wait until we implement it and we'll know when we get there? Obviously I can not take the “approximate Disneyland wait time” as you call it. I don't see it. Am I missing something? In my opinion some initial problem analysis and rough estimation is still needed. At least to see if it is doable or not. And I don't see anyone more competent to ask than development team. Sounds interesting.
I can see how this can work on a scope based project.

What about time based projects?
Simply imagine, that a customer calls and wants a new ‘take me to mars’ functionality, then wants to know how much will it cost and when can it be delivered, because time is of the essence.
We have never implemented a feature of such complexity (…and most probably never will), therefore I don’t have a clue on the effort needed.
What am I to say? Wait until we implement it and we’ll know when we get there?
Obviously I can not take the “approximate Disneyland wait time” as you call it.
I don’t see it.
Am I missing something?

In my opinion some initial problem analysis and rough estimation is still needed. At least to see if it is doable or not. And I don’t see anyone more competent to ask than development team.

]]> By: CONWIP systems | Lean Software Engineering http://aaron.sanders.name/agile/naked-planning-explained-kanban-in-the-small/comment-page-1#comment-296 CONWIP systems | Lean Software Engineering Mon, 29 Jun 2009 05:01:40 +0000 http://aaron.sanders.name/kanban/naked-planning-explained-kanban-in-the-small#comment-296 [...] If a person can be the kanban, then how about a pair? If we combine pairing and kanban with a workflow or checklist, then we get something like Arlo Belshee’s Naked Planning: [...] [...] If a person can be the kanban, then how about a pair? If we combine pairing and kanban with a workflow or checklist, then we get something like Arlo Belshee’s Naked Planning: [...]

]]>