Surviving Object-oriented Projects Official

Instead of modeling the entire world, plan by feature and build a list of tangible functionalities to deliver. 3. Invest in "Object-Think" Over Tools

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 Instead of modeling the entire world, plan by

Before writing a single line of code, identify the nature of your project to set realistic expectations and staffing: To survive, you must treat the project not

A standard system that must succeed but won't ruin the company if delayed.

Focus on picking nouns for classes and verbs for methods to stay close to the actual business problem.

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