Are there any good metaphors for explaining project complexity to a non-programmer?
It was just mentioned that I'm "not exactly building the Sistine Chapel." This is true, but I am building a freight management application, which isn't exactly as simple as drawing controls on a form (even though the vendors would have you believe it is).
I don't hold this against the person who said it, but I do feel the complexity of what I'm doing is a little misunderstood, or that statement would not have been made.
Are there any good metaphors which might illustrate a project's complexity to non-programmers?
Answer
The speaker almost certainly really meant "painting the Sistine Chapel [ceiling]". Are there any meaningful parallels?
Michelangelo had some problems with the scaffolding suggested by the original architect. He ended up constructing his own framework.
Michelangelo was a sculptor and he had to learn fresco painting in order to complete the commission.
Pope Julius II originally wanted 12 figures painted, of the apostles. Michelangelo negotiated a free hand in choice of subject matter, and delivered Old Testament scenes depicting over 300 figures. He did all the painting himself.
The project continually ran out of money(because the Pope kept waging war with the surrounding states).
So let's see. Heavy dependency on a technical prima donna, cashflow problems, not delivering to the client's specifications... You're right, it sounds like no software project I ever heard of.