the blog for developers

The only thing that really matters in software development.

Catchy title? I mean it. After 25 years of programming, the only thing that really matters in software development is if a company understands the project triangle. That from the three variables scope, time and resources you can only define two. There are two kinds of companies. Those that understand this and those that don’t. Everything they do flows from there. This is what really matters about software development.

Update: There are a lot of other factors, probably people being one of the most important (think “Peopleware”). Without understanding the Scope-Time-Resources triangle your development won’t work. It just can’t. You can screw up by chosing the wrong architecture, or methodology, or screw up during requirement engineering or with the wrong language for the problem.

But from my point of view this triangle is like gravity. If you ignore gravity, all else will fail.

You can leave a Reply here. Of course, you should follow me on twitter here.

You can share this post!
Do you want to tell others about this article? Use the social bookmark icons to submit this artice to the service of your choice. Thanks.

About the author: Stephan Schmidt is head of development at brands4friends. He has more than 15 years of internet technology experience and 10 years experience in agile. He was head of development, consultant and CTO and is a speaker, author and blog writer. He specializes in organizing and optimizing software development helping companies by increasing productivity with lean software development and agile methodologies. Want to know more? All views are only his own.
Leave a reply.

Comments

BF

Something like “The only thing that matters in live is keep breathing?”

Kind of thought bubble, isn’t it? There are lots of things that matter that mostly relate to each other in a way or even are the same at last. For instance, what about
“The only thing that matters in any whatsoever area are the persons involved?”

stephan

Yes, people are important.

But from my view, if you don’t understand the Scope-Time-Resources Triangle, your software projects won’t work. You will be overtime, overbudget, burned out but not successful.

french_c

Stephan: While your triangle is important it does not matter unless there is someone in charge who enforces it’s consequences. So if you ask me what matters in software development I would answer: A project manager with guts.

stephan

french_c: yes, you’re absolutely right. The problem with the triangle is not the triangle but project managers without guts who don’t enforce it’s consequences.

stephan

@french_c: does your business allow for some beer? ;-)

french_c

Beer, yes, of course. I am planning for a beer or two second week of June. The usual suspects. (I’m on vacation before).

Warg

Yeah Beer!

stephan

Ah, at last something that interests olli ;-)

Jason

I am not so sure. And that is because success in a software project is not really about how well managed the project or if was delivered with sensible constraints.

I can fail badly with my triangle and still deliver a system that works. I can over run. I can cost far more than I intended but when it gets there it blows the competition out of the water. And that is a successful project.

Every now and again some programmer sits down and invents something that blows everything else out of the water, that transforms a whole industry. That developer might have crystalised decades of experience (such as the developers of Writely (now part of google docs)) or had a Eureka moment (maybe the web itself).

I would suggest that it is not so much an iron triangle as a very good rule of thumb that is foolish or brave to ignore.

So back to your title – the only thing that matters is success. trite but true.

Leave a Reply

What people wrote somewhere else:

Additional comments powered by BackType

Guide to CodeMonkeyism

Over the last 4 years I wrote many articles on this blog. To make it easier for you to find the relevant ones, I've organized them into topics.

Top 10

6 reasons why my VC funded startup did fail

Go Ahead: Next Generation Java Programming Style

Java Interview questions: Write a String Reverser

The dark side of NoSQL

7 Bad Signs not to Work for a Software Company or Startup

Is Java dead?

Scala vs. Clojure

Never, never, never use String in Java

No future for functional programming in 2008 – Scala, F# and Nu

Clojure vs Scala, Part 2

Job Seeker

Another Good (Java) Interview Question

7 Bad Signs not to Work for a Software Company or Startup

Java Interview questions: Write a String Reverser (and use Recursion!)

Java Interview questions: Multiple Inheritance

As a Manager: What I value in developers

Top 10 Tips (+1) to Get a Pay Raise

Java Developer

Is Java Dead?

Go Ahead: Next Generation Java Programming Style

Be careful with magical code

All variables in Java must be final

Never, never, never use String in Java

Bending Java: More readable code with methods that do nothing?

Startup/CTO

Development Dream Teams

6 reasons why my VC funded startup did fail

American vs. European style of Software Development

12 Things to Reduce Your Lead Time and Time to Market

The high cost of overhead when working in parallel

Essential storage tradeoff: Simple Reads vs. Simple Writes

Agilist

What Developers Need to Know About Agile

5 Practices Better to Change in Your Scrum Implementation

Scrum is not about engineering practices

ScrumMaster and ZenMaster: The joke of certification

What is Trans-Scrum?