Finally the project is nearing the end and handovers are being planned, kick-out dinner is booked and the next project is being staffed up. But there are still some open defects, how can this be?
Shouldn't we deliver a complete software, there should not be any defects, or ?
As stated over and over testing can continue until the fingers bleed, and yet there will be new issues found or some issues might not have been solved. So how do you handle this ?
A good handover is the key, and as usual good communication. The receiving organization must be aware of the current status and if they can accept a delivery with open issues. Also there should be a plan for handling these open issues.
Usually some tool is used for tracking issues during development, QC, Jira or similar. But when it's handed over to maintenance, they might not use the same tool, or the issue handling process is completely different as the product is now in production.
Make sure the open defects are clearly described with steps to recreate.
Ensure that when handover is done that the receiving organization understands the issue and the possible impacts. Also make sure that they understand the issue, what seems obvious to you might not be for another person.
Good practice is also to do a follow up later to see how these issues have been handled. As it is easy to forget and if not fixed they will come back in one way or the other.
No comments:
Post a Comment