Situation: So, we are now doing daily stand ups and did the first retrospecive after a long time. Each team member was asked to put out their Sads ☹️ and Glads 😊 for the past sprint. But because it was the first time in a long time, we came up with a really long list from since the beginning. But the most Sad that I think needs to be addressed first was:
The QA team feels their role is neglected
Currently, we have three teams, i.e. devs, qa, implementors. QA team is supposed to be the bridge for the devs and implementors. QA files the feature requests and bugs found by them and implemetors. Devs deliver the updated version then QA performs tests and, if pass, releases to the implementors. What currently happens is that because of strict deadline, implementors are forced to use untested versions. I know. I know, sorry. But also, when the user discovers a bug, which is expected, the QA team takes the blame from the Project Manager. 🤢
What's the solution?
It's obvious that our process flow needs to be reconstructed. So I'm thinking of taking the QA team as the internal QA with the devs which will comprise the whole R&D team. Devs and QA are to work closely together to deliver the software. QA are to perform integration and funtional testing before devs can merge their changes to master repository (we are using git, btw). But. But. But I am thinking, as a dev, what a setback! Now, I need code review and QA approval to complete my pull request. I know I said 'work closely together', but still. Maintaining a develop branch also looks like an option. But I think that's just putting the load somewhere else on someone else. I know there should be something we can do about this. Maybe a new process flow? Maybe just restricting the implementors to access the builds? Help. 🙏