[hand with pencil]
Stuff For Sale
2004 Summer Tour
About
Blog
Class Stuff
Email Me
Events
Gallery
Home
In The Press
Newsletter
Services
Smalltalk
Veggie Van Gogh

Credits
© 2002,
Bytesmiths

[this is simply a banner and menu bar]

Please patronize sponsors of this page!

Bytesmiths no longer is involved in software consulting. Maintenance of this web site is currently subsidised by unrelated business activities. Please pass the word to other interested folks, so I can continue to host this page!
Your site could be listed here, for as little as $12 per month! Go to Bytesmiths Press for details.

This site has been selected by PC Webopaedia as one of the best on this topic!
This site has been awarded a Links2Go Key Resource Award in the Smalltalk category!

[ prev | top | next ]

Nothing Is Ever Finished

(This is a slide show. You really won't get 
anything out of it unless you have a graphical web browser with graphics turned 
on.)
- "...inexperienced programmers were able to learn the technology, be productive, and not worry about the system being perfect the first time." [Cupparo 93]
- This syndrome is often called "the death spiral" by those who are unable to establish the proper exit criteria. We submit that those organizations are equally subject to the "over Niagara in a barrel" syndrome when using traditional waterfall techniques!
- A spiral process lessens, rather than increases, the risk of running off the end of the schedule without having anything to show. In a five-phase waterfall process where each phase slips 20%, you have nothing to deliver at the end of the schedule, whereas in a similar spiral process with similar schedule slippage, you should be able to deliver 80% of what you originally intended.
- Be sure to plan some contingency for contraction, revision, and polishing, or "component harvesting." Re-use takes effort, but the payoff is big. However, code written for end use is rarely re-usable without effort. Take the effort!

[ prev | top | next ]