2 ms·
If you come to the realization that work in itself isn’t evil, you can stop living your life as a waterfall-planned software project too. Nothing wrong with "w
by edw519 18y ago
If you come to the realization that work in itself isn’t evil, you can stop living your life as a waterfall-planned software project too.
Nothing wrong with "waterfall-planning" if it's done properly. Problem is, it usually isn't.
I understand that sometimes you need to release early and often. This is when you can't conduct proper anaysis. Why not? Because you're trying for a home run building something big and you don't know where your project will take you or who will eventually use it. Like a Web 2.0 or social site.
But for the rest of us, "waterfall-planning" is just another name for the Systems Development Life Cycle (SDLC), which is an excellent way to develop systems. But you must conduct analysis first. You must answer the question "what" before you examine the question "how".
Most developers do not know how to do this. How can you tell? When their waterfall phases take too long (more than a month for analysis for most projects). When they say things like, "The user doesn't know what he needs." Yes he does. You just have to keep digging until you know.
Once a good programmer learns how to conduct analysis he becomes a good developer. Then projects become like shooting fish in a barrel. You biggest problem will be convincing your customers that you can do what they think can't be done.
- run4yourlives 18y agoYou've just highlighted everything wrong with the waterfall method, and the SDLC for that matter. You said it yourself: Most developers don't know how to perform the level of front loaded analysis required for a successful SDLC project. Ergo, "most" waterfall methods fail miserably. The method is out of sync with how humans work. When your process boils down to creating a team so elite that they would succeed regardless, it's not much of a process.
- edw519 18y agoThe method is out of sync with how humans work. Wrong. The method works perfectly when done properly. Because it's perfectly in sync with how humans work. So why don't most people know how? 2 possible reasons: - All we really have to do is stay one step ahead of the users. So we don't have to be very good. - The field is so young we still don't have adequate well-established standards and procedures. Imagine "release early and often" as the standards for law, medicine, or bridge building. I've heard this argument too many times from people who have never done it right so they think it can't be done.
- run4yourlives 18y agoYour argument is contradictory and therefore self-defeating. If the method was in sync with normal work patterns, we wouldn't be having this discussion.