Surviving Object-oriented Projects -

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

Avoid deep inheritance hierarchies (more than two levels is often "brittle") and prefer composition to keep the system maintainable. 4. Manage the Human Element Develop in small, testable chunks that result in

Organizations often spend thousands on CASE tools while neglecting the developers' mindset. Training developers in "object-think"—the ability to model problem domains effectively—is the single most significant cost but also the highest predictor of success. Avoid deep inheritance hierarchies (more than two levels

A high-stakes move to transition the entire organization to an OO paradigm. 2. Adopt the "Incremental" Habit

A small, elite team tackling a highly difficult, isolated problem.