Member-only story
Work
Why Every Developer Dreads Project Delivery
And how to fix it.
I think many will agree with me that the project delivery stage is the most difficult. Customers check and find bugs, and developers fix them. If the customer checks in parts, the programmer must be distracted from other projects.
Emotions run high, especially in the low-price segment, where the customer has no experience in development and the programmer has no negotiation skills.
Today, I will tell you how we minimize the number of bugs during delivery without wasting a lot of nerves, money, and time.
The more iterations in the format “found errors — fixed — sent to check again”, the more emotions run high. From the customer’s side, it looks like this: clumsy programmers cannot fix their own mistakes, and from the programmer’s side, the customer cannot sit down and check everything at once, sending a single bug list for the project.
How testing is done in most teams
Let me make it clear right away that by the majority,y I mean teams working in the low and medium price segment. However, this approach is also found in some high and premium segment studios, where an application costs from $15k.