Re: agile development and frameworks
- From: "Ilja Preuß" <it@xxxxxxxxxxxxx>
- Date: Mon, 21 Nov 2005 19:06:14 +0100
Mike Gaab wrote:
> My tendency is to use those things that I already know
> work. I am always looking for a better way but if I have something that is
> sufficient, I
> usually go with it.
That reduces the risk of getting a solution that is worse than the known
one, but also has the risk of not finding that revolutionary better solution
your competitor might find. Those two risks need to be balanced, and I think
finding that balance isn't trivial. And it's even a recursive problem,
because you have to decide wether to go with the balance you are used to, or
try to shift it a bit to see what happens...
One way to shift the balance is to find ways to make experimentation more
safe, so that you aren't screwed up when it fails. Techniques to do that
include spikes (controlled, time boxed experiments), having Slack, keeping
your options open so that you can switch to a known-to-be-good solution,
trying different approaches in parallel, etc.
Cheers, Ilja
.
- Follow-Ups:
- Re: agile development and frameworks
- From: Mike Gaab
- Re: agile development and frameworks
- References:
- agile development and frameworks
- From: Michael G
- Re: agile development and frameworks
- From: Ilja Preuß
- Re: agile development and frameworks
- From: Mike Gaab
- agile development and frameworks
- Prev by Date: Re: Decouple SQL queries from class in OOP design
- Next by Date: Re: Decouple SQL queries from class in OOP design
- Previous by thread: Re: agile development and frameworks
- Next by thread: Re: agile development and frameworks
- Index(es):
Relevant Pages
|