A Macro Level Perspective of Software Development


February 9, 2011

Why is delivering good software on a consistent basis hard? There are many existing answers to this question already. This is our version. A list of things good software should achieve:

Update: We’ve now migrated to James Shore’s definition:

Success is usually defined as delivering on time, under budget, and as specified. That’s a flawed definition. Many late projects are huge successes for their organizations, and many on-time projects don’t deliver any value. Instead, think in terms of organizational, technical, and personal success.

What it takes to build such software:

Our version of the software life-“cycle” :-) : softwaredev