qualidade de software
Software quality? What, when and how should we care?
Sept. 5, 2018Maicol Peixe
Prototyping, MVP, billing, investment, business management and cash flow, all part of the day-to-day life of a startup, but one of the most critical points that is usually overlooked is "Software Quality", which despite being knowledgeable of all tends to be left aside and only remembered in moments of desperation, which may impact on new investments and even make the business continuity unfeasible.
There are many factors that make us sin with the low level of caution and attention applied to the theme of Software Quality, among them, the lack of clarity of the need for testing, present to the methodologies, models and tools used for the planning and structuring of startups.
We never think of developing our products and services, that they deserve specific attention, that goes far beyond the basics, and that we need to carefully evaluate their behavior in order to be safe, whether in the presentation to a group of family investors, an angel investor or bigger steps along with accelerators, Venture Capitals or even an IPO.
A simple flaw can lead to the depreciation of your dream value, thereby reducing the value of your company in the investment negotiation process. Imagine a pitch where we have a flaw in the middle of the presentation, imagine shame, disappointment, imagine a problem after a marketing investment, which is often one shot, existing customers leaving the boat, potential disappointed customers, and still the media describing, in a clear, truthful and objective way, the failure of their work.
There are market data, I'm not talking about dreams or kicks, but the hard reality, which I understand, we can all avoid. According to Optima Specialty, 95% of customers share their bad experiences (http://optimaspecialty.com/), while PWC (https://www.pwc.com/) reports that, globally, 30% of customers who face a single bad experience cease to use the service. Additionally, more than 50% of customers leave the boat after more than one bad experience, the situation is chaotic and it is very important to understand that this does not only consider a company with angel capital or family capital, we are talking about companies of all kinds, segments and sizes, that is, it is never early and certainly it may be too late to start worrying. Take for example what happened with WhatsApp that had a loss of nearly 5 million users for the Russian Telegram app in just a single day due to the instability presented by the application.
The risk and cost of not adhering to quality are very high, as we can see in "The Art of Software Testing, 2012" where it is presented that the costs arising from quality problems can reach 100 thousand times if considered data arising from reputation, loss of revenue, contracts and the like.
As presented, when we frame our dreams and focus on making them real, we usually do not stick to the theme, since tools such as Canvas Model, Lean Canvas, Jobs to Be Done, P & L do not instruct us clearly and objectively to perform with tests , and this makes us run without taking care of the route traveled, without the caution necessary so that there is no risk of having to go back several steps.
For each stage of maturation, each level of investment, each number of users there is a differentiated approach, a specific way through which we can structure ourselves, focusing on points of greater importance, that will help us in that specific moment that we are walking and fighting for our success.
For a greater clarification of all, through the next articles, we will address the specific level of importance of each test at a certain moment in the level of maturity, presenting which themes, processes and tools can and should be used, without damage to the speed of development, but with great gain in reducing the risk of failure and rework.
What we will present is the way of the stones so that the quality performance curve can be reversed, drastically reducing the investment and the risks of failure after a certain level of maturity, either of the product or the service, through the analysis of the relationships between time, investment, user concentration, focus areas and goals.