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,
Surviving Object-Oriented Projects: Cockburn, Alistair - Amazon.com Surviving Object-Oriented Projects
A small, elite team tackling a highly difficult, isolated problem. Building a successful object-oriented (OO) project is less
An experimental project designed to identify future implementation hurdles. Organizations often spend thousands on CASE tools while
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.
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.