Have you ever been involved in a construction project? Everything is defined upfront and scheduled out in minute detail. Look at blueprints and you'll see where every lightswitch, wall socket, door jam will go. The exterior is specified and drawn out. Site plans show how to grade the land, how far back on the lot the building will sit. It's all waterfall management.

You just can't do software that way. How many times does software come in over budget and late. Using Agile techniques you can eliminate many of these issues. Don't plan things in detail. Do you plant a tree and plan where every leaf will go? Sometimes you need to prune trees. You do this with code, it's called refactoring. You need good soil for your plants to grow well. That's good OOP usage.

Code grows and changes in unpredictable ways, as do plants. Plants need to be cared for and nurtured. So does your code.

There are other comparisons, but I don't want to give away the entire presentation.

>It's hard for me to dispute that without even knowing what the phrase means. Google offers no help. Can you offer a definition of software gardening?
>
>I've got a garden which is being devoured by wabbits. They are systematically destroying my tomato and pepper plants and chewing up the flowers. When I show up they run under the fence. Cindi, who knows a thing or two about wabbits, arrives tomorrow and we are going to take them on.