Comments on: An Agile pitfall – starting a project too soon http://machielgroeneveld.nl/?p=29#utm_source=feed&utm_medium=feed&utm_campaign=feed Conscious Development Tue, 23 Mar 2010 21:37:57 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Patrick Verheij http://machielgroeneveld.nl/?p=29&cpage=1#comment-7 Patrick Verheij Sun, 30 Aug 2009 20:18:12 +0000 http://machielgroeneveld.nl/?p=29#comment-7 <a href="#comment-6" rel="nofollow">@Machiel Groeneveld </a> I agree with the pre-project BC draw up. Agile does support killing projects though. You create results quickly. If you aren't able to create results you are either not doing agile or the project should be killed. So agile practice is nothing but helpful to unmask projects that should not be projects and thus should be killed. I agree that the killing itself is *not yet* in any agile method I know of. I sense an opportunity...:) @Machiel Groeneveld
I agree with the pre-project BC draw up. Agile does support killing projects though. You create results quickly. If you aren’t able to create results you are either not doing agile or the project should be killed. So agile practice is nothing but helpful to unmask projects that should not be projects and thus should be killed. I agree that the killing itself is *not yet* in any agile method I know of. I sense an opportunity…:)

]]> By: Machiel Groeneveld http://machielgroeneveld.nl/?p=29&cpage=1#comment-6 Machiel Groeneveld Thu, 27 Aug 2009 19:45:42 +0000 http://machielgroeneveld.nl/?p=29#comment-6 <a href="#comment-5" rel="nofollow">@Patrick Verheij </a> Just to make things clear, the pre-project phase is (in my mind) the phase where you draw up, amongst other things, the business case. Killing projects is hard and usually you're not likely to change that. More importantly, Agile doesn't help us out with project-killing-strategies. @Patrick Verheij
Just to make things clear, the pre-project phase is (in my mind) the phase where you draw up, amongst other things, the business case.

Killing projects is hard and usually you’re not likely to change that. More importantly, Agile doesn’t help us out with project-killing-strategies.

]]> By: Patrick Verheij http://machielgroeneveld.nl/?p=29&cpage=1#comment-5 Patrick Verheij Thu, 27 Aug 2009 14:05:55 +0000 http://machielgroeneveld.nl/?p=29#comment-5 A very interesting dilemma, Machiel. And very well reflected upon. In my humble opion, there's no real issue here. You can always _kill_ a project right after the first results tell you that it leads to too little value or no value at all. You can always start a project after you finish a business case. You always do have at least a BC before you start, don't you? Anyway, the real problem here is _killing_ the project. That isn't done easily. Once people set their mind on creating something, no matter if they have a sense of real value, they commit themselves to either the work or the dream and stopping suddenly isn't an option anymore. My approach would be to institutionalize different ways to kill projects sooner. Or is that just a workaround? :) A very interesting dilemma, Machiel. And very well reflected upon. In my humble opion, there’s no real issue here. You can always _kill_ a project right after the first results tell you that it leads to too little value or no value at all. You can always start a project after you finish a business case. You always do have at least a BC before you start, don’t you? Anyway, the real problem here is _killing_ the project. That isn’t done easily. Once people set their mind on creating something, no matter if they have a sense of real value, they commit themselves to either the work or the dream and stopping suddenly isn’t an option anymore.

My approach would be to institutionalize different ways to kill projects sooner. Or is that just a workaround? :)

]]>