When a new feature is close to a deadline, and you ask the question: “how are we doing?” There are three levels of done you can get:
- The developer’s done: it means the feature is code completed, but potentially untested, and likely with some bugs.
- The QA engineer’s done: the feature was tested, but it needs the user’s feedback, and there is a chance that won’t work as expected in the production environment.
- The user’s done: this never truly happens. The user might be happy with the new feature, but if the user is committed enough to the product, she will provide some good feedback about making it better.
If you really wanna know if the feature will be on time, you should aim for the QA engineer’s done. If you don’t have a QA engineer in your team, the second best guess is the developer’s done.
Founder & CEO at InTheValley
With a +20-year in tech, I'm dedicated to transforming advertising for startups, helping them grow and succeed in the AI age.
Latest posts by Leo Celis (see all)
- Role of AI in Threat Detection and Response within DevSecOps - 04/25/24
- AI-driven Personalization in AR Ads - 04/24/24
- ML Models for Threat Prediction in Ads - 04/23/24