5. Develop without capacity/performance requirements

At least a vague estimate of how many users will use a software isn't just good practice but is basic business forecasting. To develop a reasonable load test, you need performance expectations. You need to know how many users the system should be expected to handle.

4. Wait until the end to engage users

In marketing, someone has to validate that the product development group has hit the mark and someone is going to buy it. It is the same way in software. Although, it can be embarrassing and troublesome to show your software in a "rough state”, someone needs to make sure the end product will pass muster with users as early as possible.

3. Try to buy your way out of software development

It is a fact that commercial apps make more sense than internal app dev in some cases. But it's also possible to license, say, the entire Oracle or WebSphere stack and deliver absolutely nothing. There's a limit to how much stuff your development team can actually absorb and use before the complexity of the stack outweighs any supposed technical benefits.