3 days of planning, 5 days of execution and then the whole work gets stuck for weeks on QA. On the flip side if it gets picked up, it results in ...
For further actions, you may consider blocking this person and/or reporting abuse
devs should always own the code and never throw crap over the wall to be tested.
that said there is no left or right approach. dev needs to be responsible for coding and unit testing and automation. QA is there to be sure all requirements are met as a extra set of eyes 👀 for the development and PM.. keep everyone honest.
That is spot on! All efficiency approaches are bespoke to the context ☺️
Shift left is fine and approach has been in use for some time. QA is never a bottleneck if the code quality you build is good. And, if your code quality is good and QA taking more time to validate then you need to review the efficiency and skills of testers, and fix the team accordingly with right testing skills.
You're right! All process improvements are bespoke ☺️
This is the age old issue....Dev takes their time to create, QA is always the bottleneck. Solution, create an accurate project plan, follow it and adjust it when situations happen when something takes longer than expected. Keep management informed. And, when deadlines have to be met, the team puts in the extra effort and in some instances you drop features to make deadlines. You need QA....recall recent issues last week. That was a failure in the development, QA and release process. Final thought, the most successful projects are, when DEV and QA are working together. The writer of this article sounds like they work in a Waterfall development environment. They may want to try Agile development . It's a team approach to development.
Shifting left is one of those things that feels so obvious once someone says it to you. 👏
Great post! The struggle with QA bottlenecks is real. Loved the idea of shifting QA left and having devs own their code. Collaborating better and looking back for improvements can make a huge difference. Thanks for sharing these tips!
Oh yeah. I've seen an impact of this pretty instantly at one of my previous jobs.
the genie is out of the bottle!
Wonder post , can we shift the ITIL to UP or DOWN as well as kind of shifting coz they need to be automated Lol... Waiting to your article about it
Haha!
Although automation comes slightly later when the use cases are solidified. For the fresh features, it's generally and rightfully on a lag
Devs can be good at writing test plans. QA engineers who do not test anything should not even exist. Just ditch them.
💯
Well done! QA is something that can start from the design/requirement state
What if it's the opposite and there isn't enough QA resource?
Then someone needs to prepare the test plan. The devs then ☺️
The ones I have used or as a concept?
"Manual QA"
There's your problem. Get SDETs.