Surviving Object-oriented Projects | 4K · 360p |

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.

Avoid deep inheritance hierarchies (more than two levels is often "brittle") and prefer composition to keep the system maintainable. 4. Manage the Human Element Surviving Object-Oriented Projects

A standard system that must succeed but won't ruin the company if delayed. The survival of a project often hinges on social factors

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. To survive, you must treat the project not

The most common cause of OO project failure is the "big bang" release. Surviving projects focus on: