Develop in small, testable chunks that result in running code.
Many teams transition to object technology expecting a "silver bullet" for productivity, only to find themselves trapped in refactoring loops or complex inheritance hierarchies that make the codebase brittle. To survive, you must treat the project not just as a technical challenge, but as a management and cultural shift. Surviving Object-Oriented Projects
The most common cause of OO project failure is the "big bang" release. Surviving projects focus on: Develop in small, testable chunks that result in
Before writing a single line of code, identify the nature of your project to set realistic expectations and staffing: The most common cause of OO project failure
The survival of a project often hinges on social factors. Research shows that many failed projects are saved only when new "core developers" step in to assume ownership.