Happy Independence Day to all Indians across the Globe.
And Happy Independence Day to all Indian Software Testers across the Globe.
What does freedom mean to all? Freedom to do anything within the purview of the Law. In the software testing context, freedom to a tester means to do anything within the purview of the scope of testing, and sometimes, beyond that.
Any software tester needs that freedom to achieve a goal. Goal is Quality. Tester needs freedom to explore everything and unearth bugs. Tester needs a free hand to explore, experience and experiment the application under test.
I am somehow against holding a tester responsible for duplicate or rejected bugs. That's against the freedom of a tester. What's the big deal with a duplicate bug or a rejected bug. The customer is equally responsible for the quality of application. The tester is not responsible when the requirements are not frozen (freezed)(finalized)(baselined), the customer is.
The customer or the stakeholder should understand that a tester is there to test the application and find bugs, not to face enquiry committees for duplicate bugs, rejected bugs, leaked bugs.
Unless the tester is a free bird to test what he wants, how he wants, any barriers would discourage a tester to do a good job in testing. Let alone do a good job, a tester would think twice before plunging into a testing job.
16 August should be called as INDIAN SOFTWARE TESTER'S DAY, a day after the Freedom day of all Indians.
Thoughts?
Jai Hind!!!
Total Pageviews
Monday, August 15, 2011
Monday, August 08, 2011
SOFTWARE QUALITY – IT TAKES TWO HANDS TO CLAP
This point of view tries to define the common pitfalls of Software Quality and the stakeholders’ involvement in achieving the quality objectives of any Software Development Engagement. Quality per-se cannot be achieved with just planning without action, the action from all the stakeholders. The author tries to find out who should be the stakeholders for achieving quality objectives and if the current set of quality initiatives taken by organizations is sufficient to reach the goal or will the organizations have to re-think on their plans.
SOFTWARE QUALITY – IT TAKES TWO HANDS TO CLAP; the title looks vague. But in reality, it is not as vague as we think. As a tester, I don’t think it is vague. What are the “two hands” that we are talking about? Well, one hand is the “Customer” and the other hand is the “Service Provider”. By saying that, does the title still make sense? Enough is said about co-operation between two business entities. But, will there be success when both work in tandem? The answer to this is a plain YES. Software solution will reach its peak of Quality with co-ordination and understanding between the Customer and the Service Provider. We may wonder then that this happens every time but there are cases where customers are not happy with Quality of the solution. Probably, they would have stumbled upon severe production bugs. We know that we used the right processes, right approach and right mix of everything. But still, there is no “quality” as perceived by the Customer.
The domain, the technology, the software model, the people, the process, the testing and quality initiatives – these are all necessary phases of any Software Development. Each of these is focused from the day one of the Software Development Life Cycle. I am sure then the Customer too is an equal stakeholder in the entire process. After all, the customer pays for the service. But we often miss something or rather many things during the process of execution. Some of the important factors that we often neglect are:
Attitude
Communication
Tracking
Follow up
Understanding
Approval
Recognition
Resources
Tools
Documentation
Process
Technology
The order could be different in each case. The list could grow with each experience. But these form a major chunk of misses that could be possible “fatal errors”.
SOFTWARE QUALITY – IT TAKES TWO HANDS TO CLAP; the title looks vague. But in reality, it is not as vague as we think. As a tester, I don’t think it is vague. What are the “two hands” that we are talking about? Well, one hand is the “Customer” and the other hand is the “Service Provider”. By saying that, does the title still make sense? Enough is said about co-operation between two business entities. But, will there be success when both work in tandem? The answer to this is a plain YES. Software solution will reach its peak of Quality with co-ordination and understanding between the Customer and the Service Provider. We may wonder then that this happens every time but there are cases where customers are not happy with Quality of the solution. Probably, they would have stumbled upon severe production bugs. We know that we used the right processes, right approach and right mix of everything. But still, there is no “quality” as perceived by the Customer.
The domain, the technology, the software model, the people, the process, the testing and quality initiatives – these are all necessary phases of any Software Development. Each of these is focused from the day one of the Software Development Life Cycle. I am sure then the Customer too is an equal stakeholder in the entire process. After all, the customer pays for the service. But we often miss something or rather many things during the process of execution. Some of the important factors that we often neglect are:
Attitude
Communication
Tracking
Follow up
Understanding
Approval
Recognition
Resources
Tools
Documentation
Process
Technology
The order could be different in each case. The list could grow with each experience. But these form a major chunk of misses that could be possible “fatal errors”.
Friday, August 05, 2011
Bug Burji
All about Testing (not your patience) Software and the Bugs and Burji. The stories and what not.
Subscribe to:
Posts (Atom)