Surviving Object-oriented: Projects

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.

Develop in small, testable chunks that result in running code.

Before writing a single line of code, identify the nature of your project to set realistic expectations and staffing: Surviving Object-Oriented Projects

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

A high-stakes move to transition the entire organization to an OO paradigm. 2. Adopt the "Incremental" Habit The survival of a project often hinges on social factors

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

Building a successful object-oriented (OO) project is less about mastering syntax and more about navigating the human and structural "holes" that swallow most software initiatives. Based on the principles in Alistair Cockburn's seminal work, Surviving Object-Oriented Projects , and modern industry insights, Before writing a single line of code, identify

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.