The overall quality of a software product is not visible to the naked eye. The UI itself may look great and it also may work as intended. But as the software grows, it gets more complex. In practice, quality assurance gets left out in favor of a fast delivery. But this approach can introduce more costs than they save. Unfortunately, they surface much later in the product lifecycle.
Estimation is one of the hardest parts in software projects due to many misconceptions, the inability of humans to estimate, and the risk and fear of losing your margin. A systematic approach and the knowledge of typical mistakes will drastically improve your estimations and allow for win-win-projects.
Building a web application (web apps) can be a daunting task. It includes so many decisions that it’s easy to quit before even starting. Here is an essential guide to building a great basic web application and avoid common pitfalls.
Why should I care about good software?
It’s all about the money! — Or, to put it in less capitalistic terms, it’s about preserving resources, which primarily is everyone’s time.
A recent example is a software project of the German employment agency that was canceled after spending 60 million euros. — For example, the software has not been flexible enough to change a bank account number without deleting the full record and typing it in again with the new number.
What is great software?
We’re talking about ‘great’ software here. Great software means the optimum of costs, features, and time spent.
How can I make sure that software works?
The most important thing is to ‘bake’ quality into the process and into the people. This is why the improvement of your development process is crucial.