Surviving Object-oriented Projects • Extended

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

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,

Avoid deep inheritance hierarchies (more than two levels is often "brittle") and prefer composition to keep the system maintainable. 4. Manage the Human Element Surviving Object-Oriented Projects

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

Surviving Object-Oriented Projects: Cockburn, Alistair - Amazon.com Before writing a single line of code, identify

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

A standard system that must succeed but won't ruin the company if delayed. Manage the Human Element A high-stakes move to

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