Comments on: Kanban State of Mind http://blog.mattwynne.net/2009/05/27/kanban-state-of-mind/ Matt Wynne taking it one tea at a time Fri, 27 Jan 2012 08:31:34 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Lisa Ray http://blog.mattwynne.net/2009/05/27/kanban-state-of-mind/comment-page-1/#comment-932 Lisa Ray Mon, 29 Mar 2010 19:45:17 +0000 http://blog.mattwynne.net/2009/05/27/kanban-state-of-mind/#comment-932 <p>Good description of Kanban.</p> Good description of Kanban.

]]> By: David Joyce http://blog.mattwynne.net/2009/05/27/kanban-state-of-mind/comment-page-1/#comment-643 David Joyce Tue, 23 Jun 2009 10:55:30 +0000 http://blog.mattwynne.net/2009/05/27/kanban-state-of-mind/#comment-643 <p>I totally agree with you Matt, I just think its misleading to say Kanban = no iterations/timeboxes. Kanban is a set of principles of which this isnt one.</p> I totally agree with you Matt, I just think its misleading to say Kanban = no iterations/timeboxes. Kanban is a set of principles of which this isnt one.

]]> By: Karine Sabatier » Blog Archive » Links w#24 http://blog.mattwynne.net/2009/05/27/kanban-state-of-mind/comment-page-1/#comment-625 Karine Sabatier » Blog Archive » Links w#24 Tue, 16 Jun 2009 07:41:24 +0000 http://blog.mattwynne.net/2009/05/27/kanban-state-of-mind/#comment-625 <p>[...] Kanban philosophy in a few words Last point refers to what I used to call the “my wife doesn’t like your design” symptom. Collect the data you need in time to make responsible decisions. Repeat. Collect the data you need in time to make responsible decisions. And sometimes, just regard it and trust your instinct. [...]</p> [...] Kanban philosophy in a few words Last point refers to what I used to call the “my wife doesn’t like your design” symptom. Collect the data you need in time to make responsible decisions. Repeat. Collect the data you need in time to make responsible decisions. And sometimes, just regard it and trust your instinct. [...]

]]> By: Matt http://blog.mattwynne.net/2009/05/27/kanban-state-of-mind/comment-page-1/#comment-605 Matt Wed, 10 Jun 2009 08:24:03 +0000 http://blog.mattwynne.net/2009/05/27/kanban-state-of-mind/#comment-605 <p>@David a common anti-pattern I see on agile teams is where, because of the pressures of the timeboxed iteration, they defer work that has no obvious immediate value, like refactoring and other technical debt resolution. This work, which as we all know in the medium-long term will help the team increase or at least sustain their pace, is abandonded because of the urgency of meeting the immediate deadline of the end of the sprint. Eventually the team's pace splutters and chockes as the friction of all that technical debt slows them down.</p> <p>To me, this is one of the key characteristic differences about using a kanban system: there is nowhere to hide this stuff. Either it is important, in which case you do it now, or you agree it isn't actually necessary and don't do it at all. There is no 'someday / maybe' list for the team.</p> @David a common anti-pattern I see on agile teams is where, because of the pressures of the timeboxed iteration, they defer work that has no obvious immediate value, like refactoring and other technical debt resolution. This work, which as we all know in the medium-long term will help the team increase or at least sustain their pace, is abandonded because of the urgency of meeting the immediate deadline of the end of the sprint. Eventually the team’s pace splutters and chockes as the friction of all that technical debt slows them down.

To me, this is one of the key characteristic differences about using a kanban system: there is nowhere to hide this stuff. Either it is important, in which case you do it now, or you agree it isn’t actually necessary and don’t do it at all. There is no ‘someday / maybe’ list for the team.

]]> By: David Joyce http://blog.mattwynne.net/2009/05/27/kanban-state-of-mind/comment-page-1/#comment-603 David Joyce Tue, 09 Jun 2009 20:09:57 +0000 http://blog.mattwynne.net/2009/05/27/kanban-state-of-mind/#comment-603 <p>On the whole I agree, however Kanban does not = no iterations, its a choice.</p> <p>As David Anderson says "Kanban still allows for iterations but de-couples prioritisation, delivery and cycle time to vary naturally according to the domain and its intrinsic costs."</p> On the whole I agree, however Kanban does not = no iterations, its a choice.

As David Anderson says “Kanban still allows for iterations but de-couples prioritisation, delivery and cycle time to vary naturally according to the domain and its intrinsic costs.”

]]> By: Kanban with Pomodoro, it’s like spaghetti with sushi but it might work http://blog.mattwynne.net/2009/05/27/kanban-state-of-mind/comment-page-1/#comment-597 Kanban with Pomodoro, it’s like spaghetti with sushi but it might work Mon, 08 Jun 2009 10:05:20 +0000 http://blog.mattwynne.net/2009/05/27/kanban-state-of-mind/#comment-597 <p>[...] Yip twitted a link to this short, clever blog post from Matt Wynne defining [...]</p> [...] Yip twitted a link to this short, clever blog post from Matt Wynne defining [...]

]]> By: Kanban « The Art of Software Development http://blog.mattwynne.net/2009/05/27/kanban-state-of-mind/comment-page-1/#comment-587 Kanban « The Art of Software Development Tue, 02 Jun 2009 07:23:01 +0000 http://blog.mattwynne.net/2009/05/27/kanban-state-of-mind/#comment-587 <p>[...] So, if all this sounds cool and you want to give Kanban a shot, then apparently this is how you should get started. Also, make sure to get into a Kanban state of mind. [...]</p> [...] So, if all this sounds cool and you want to give Kanban a shot, then apparently this is how you should get started. Also, make sure to get into a Kanban state of mind. [...]

]]> By: Michael Dubakov http://blog.mattwynne.net/2009/05/27/kanban-state-of-mind/comment-page-1/#comment-575 Michael Dubakov Thu, 28 May 2009 22:52:50 +0000 http://blog.mattwynne.net/2009/05/27/kanban-state-of-mind/#comment-575 <p>Nice list. Shortest Kanban explanation I've ever seen :)</p> Nice list. Shortest Kanban explanation I’ve ever seen :)

]]>