Let's accept the fact, "You can not find all bugs just by going through requirements document".
I wrote all the test cases based on requirements document and added some more based on my experience. I got bugs, wherever system did not meet the requirements.
One day, when I Was showing the demo to a business user, He asked me to navigate to another module which was not in the scope of requirements document for customization. He asked me to check some data values and perform a workflow transaction. He was happy to see that data that he is
looking for is there.
I realized that this data is fine but it is showing duplicate records (for thousands of records). Business user did not see the duplicate record. He was just happy to see the data.
I drilled down the bug and found that the solution provided missed of doing customization in this module as this was not provided in the requirement documents. This bug turned out to be a "Show Stopper" and sent to a top ERP selling organization. They accepted the bug and are working to fix it in their product.
It is very important to have full understanding of business user's expectations. You should not stop the requirements gathering, when your requirements document is ready. Whenever you have the opportunity, discuss with business user about the product which is under development/testing/UAT
or at any stage.
In most of the cases, you have to agree to the business user's demand and your go live plan will get delayed. So, it's better to have courage and discuss the implementation with them. Else, you will have overruns in Revenue, Cost, Quality, Schedule, Resources. All !!!
I wrote all the test cases based on requirements document and added some more based on my experience. I got bugs, wherever system did not meet the requirements.
One day, when I Was showing the demo to a business user, He asked me to navigate to another module which was not in the scope of requirements document for customization. He asked me to check some data values and perform a workflow transaction. He was happy to see that data that he is
looking for is there.
I realized that this data is fine but it is showing duplicate records (for thousands of records). Business user did not see the duplicate record. He was just happy to see the data.
I drilled down the bug and found that the solution provided missed of doing customization in this module as this was not provided in the requirement documents. This bug turned out to be a "Show Stopper" and sent to a top ERP selling organization. They accepted the bug and are working to fix it in their product.
It is very important to have full understanding of business user's expectations. You should not stop the requirements gathering, when your requirements document is ready. Whenever you have the opportunity, discuss with business user about the product which is under development/testing/UAT
or at any stage.
In most of the cases, you have to agree to the business user's demand and your go live plan will get delayed. So, it's better to have courage and discuss the implementation with them. Else, you will have overruns in Revenue, Cost, Quality, Schedule, Resources. All !!!
No comments:
Post a Comment