Surviving Object-oriented Projects May 2026

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

An experimental project designed to identify future implementation hurdles.

Focus on picking nouns for classes and verbs for methods to stay close to the actual business problem. Surviving Object-Oriented Projects

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

Before writing a single line of code, identify the nature of your project to set realistic expectations and staffing: A standard system that must succeed but won't

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.

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 A high-stakes move to transition the entire organization

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.