This sprint we are trying a new thing in order to strengthen the relationship between developers and QA in the team. We are doing teams in the team, i.e. we have teamed up in two smaller teams working with their own features. So far it is going quite well, it is much more easy to focus on a specific feature and not having to pick up every release and test it. It lessens the context switching which is something that we have suffered quite severely from.
Now we are sitting together, behind us is the whiteboard with the playbook from which we can discuss changes that might have affected other areas and if the risks have changed. Also we try to update our written playbook with every release. It's quite neat actually, we increase the area that needs more testing with 1, and in the end we can see if we are testing where the risks are. It is powerful, it is visual and there is no escape. The playbook tells us if we are testing the right things based on the risks. But see here comes the problem, which is the same as before; it doesn't feel like we have enough time to test all the changes. The developers are pretty fast in writing and changing the code, and we would have to work overtime to match all the changes. But, the upside is that we don't have to. Our responsibility is to be able to present what we have tested, and it is up to the company if they want to release it. They are presented the risk, in a far more obvious way then before.
I am so glad I don't have to make those decisions, if it was up to me nothing would be released ;)
But that is enough test talk for this week, I'm off to Riga to have a lovely weekend, I hope you do too!
No comments:
Post a Comment