Problem: you have completed the project, calculated the profitability, made conclusions regarding regulations, prices and so on. And in 1-2-3 months there is an X-hour warranty, which is nowhere and is not taken into account. Waiting a few months - also not an option: our business is very dynamic. What should we do?
Our decision: to calculate the average statistics on the guarantee and put it in the budget. Say, we have the volume of warranty work about 3-5% of the total number of normal hours. Then we multiply the cost of work by 1.05 - and these risks are taken into account.
In addition, we can make a sample of managers or teams and understand who has a lot of warranty. Then we can already understand why - bad design, development, testing or project management.
Example from life: almost accidentally "caught" the guarantee of 20% of the volume of work, with several projects at once, saw that this is one manager, and figured out - why. It turns out that if you create one big task "guarantee", there can fly in anything, and this "anything" is not particularly filtered.
Front-end: $25
Back-end: $25 (PHP), $35 (JAVA, C#), $35 (Ruby, Python)
Analytics: $35 — $45
Mobile: $30
Design: $25 (designer), $35 (Art Director)
DevOps: $30
Testing: $20
