4 ms·
You're right, it's hard to correctly spec out a software project. You can't build a house without the plans. Another big factor is testing/QA. If your customer
by bluedino 8y ago
You're right, it's hard to correctly spec out a software project. You can't build a house without the plans.
Another big factor is testing/QA. If your customer service department isn't going to throughly test your new program, and nobody holds them accountable, who gets blamed on launch day when it doesn't work right? IT!
- dredmorbius 8y agoYou can build a simple house without formal plans, most especially if architect, builder, and owner/occupant are the same. Divide roles, or increase complexity of the project, or its relationships with the surrounding infrastructure, and planning or standardisation requirements escalate quickly.
- amelius 8y agoYes, you can build a simple house like that. But what if halfway through the construction, the client says they want the bathroom on the other side of the house? You'd have to redo (e.g.) all the plumbing from the ground up, location of the heating system, walls, doors, perhaps even staircases ... etc. etc.
- dredmorbius 8y agoNote that amongst my qualifiers was unity of client and builder-architect. You'll find plenty of examples of people on DIY or lone-inventor projects saying "we tried X, it didn't work, so we did Y instead. That's the unity-actor case of your hypothetical. Dividing executive-agent roles is a complexity dimension. Dividing executive (decision), design, expert (engineering), sourcing, external approval, interface, and labour/crafstmaan roles are multiple additional complexitty dimensions. And this doesn't even include the technical dimensions of the project and its infrastructure interfaces / interconnects. Complexity is interaction between components and entities.