In the past few days, I’m playing the QA role inside my team, since we have only 1 QA and lots of stories Dev Complete. It is interesting to notice when wearing the QA hat, you have other view about a story. It is not about which part of the code I should change or how should I do my tests, now it is about functionality, bugs, scenarios and so on.
It is interesting to find bugs in stories who were played by very senior developers . It makes you remember that everyone make mistakes. It is also important to see the whole story life cycle. What happens if you find a bug? Is it related to that particular story or is it something else? It should create a new card for that? If yes, how much information we should put on that? What is the priority for this bug? Should we talk with the BAs about that? Is it worth to write an automated test to make sure that bug doesn’t happen anymore?
It is very interesting how a simple thing like that, change your role for some time, make you think in a different way. If there is one thing that I noticed is that all the senior people who I have been working with, have a big picture about a story. Usually, junior people are just concerned about make stuff done and don’t think how the story can impact the whole system. Work as a QA helped me to improve this vision.
I’m looking forward to pair with a BA as well. Forget about the technical things for a moment and think only about the feature. Focus in what the user needs, how break a particular feature in different stories and keep them valuable for the client. Understand how get the requirements and “translate” that for working software and then prioritize the stories. I’m pretty sure that doing this next step, it will help me to understand even better a story life cycle.