Today Lily talked to me, when it comes due under way Ticket Detail page implemented in the 3.0 version of the first stage, when the operation of the Ticket entire page refreshes to the user experience is very bad, and then the entire solution was overthrown redone, resulting in Ticket long-delayed project than originally planned. She asked if I was aware of the problem, I thought for a moment replied fine, I was not aware of this problem, because the original version 2.0, the handling mechanisms of the page is like this, so do not feel that time has handling mechanism what is the problem. Then Lily said, Oh, is solving skills, not deal with the problem of method. Because if it is know that this is a problem, then as a Testing Leader, has not raised the issue did not go to get to the bottom of this issue is not responsible for the drive to solve the problem, then as a Testing Leader, or irresponsible in dealing with the way the problem is questionable. But if you do not know if this is a problem, then as a Testing Leader of capacity problems. Because I have not the ability to find that this is a very serious usability problems, I own practice, experience, depth of understanding of the product is not enough for me to find a serious impact on this issue will bring.
Then she added, the leadership decided after discussions held accountable, responsible and bear the blame eventually fell on the module developed by Jason body. And she also expressed their views, she believes Jason module developers should not bear the primary responsibility, should be the primary responsibility of the project manager, William, I'm responsible for project testing, as well as test manager Lily (her) body. On this issue, I agree with Lily's point of view. I think Jason to be held accountable to a person's body, it is unfair and unreasonable. I, as a person in charge of testing for problems on the project can not perceive, that in itself is a big problem, I should also bear a large part of the responsibility.
Then Lily said, as much as possible on how to prevent such problems yet. First of all, I think the root of the problem is that when the project requirements definition does not determine a good implementation of this module, without taking into account the risk here. If there is a way in defining needs to take into account this problem, then we can solve the problem at minimal cost situation. If such a problem escaped the requirements definition phase, we need to find and solve such problems during the testing phase. So, why this would pass undetected it?
I think there are two main reasons:
1, own (including the entire Testing Team) to understand the user experience and accomplishments is not enough
2, own (including the entire Testing Team) for the implementation of the established requirements and procedures too believe, can not put forward their own views or opinions have not argue but was quickly suppressed it.
So after testing process and project management process, to improve their knowledge of user experience, increase user experience testing, and then encountered feel wrong or improper design problems, to be able to, say that the idea, said come to reason, and the continued strength of their ideas implemented. If developers have objections, you can find a project leader or higher leadership. As long as you can give a reason, someone will listen to you. Of course, this is not a person I need to do, our test team everyone should have such awareness and action.
Then Lily also pointed out that the current test team there are still many shortcomings, such as team cohesion is not enough, many things are not a standard, summed up the habit of not training together, without proper accountability and performance appraisal. She also hopes the company can be a more powerful test manager to lead the team forward.
She also said not settle for mediocrity, or else many years have passed and soon found myself really mediocre. A few days ago just to see a word, moderation of the people, will become cannon fodder.
Reproduced in: https: //www.cnblogs.com/henryhappier/archive/2011/05/03/2035698.html