How common is QA used as a punching bag? Can QA be held responsible for the project delays???
Is it a healthy practice to have a tame QA Manager (aka rubber_stamp) report into SW Engineering Development Director (aka nut_cracker)?
Share….your story @@@ Dell**^^^^^
You can always email any concerns early to the product owner for a 'for sale' hw/sw item and for an internal tool, the VP or Executive running the business organization using it is usually remarkably responsive. Most internal programs and projects have 'non IT' focused program meetings where this type of concern would be very appropriate to bring up to the business or product owners. Not all meetings are in the details of feature and code reviews!...you just need to find out who owns overall responsibility. Dell/Dell EMC have very easy to navigate internal directories.
horrifying to read freshers plight.. sorry bro. are there any internal grievance forum?
I joined as fresher in Dell India Storage two years ago. working now on so called scrum project. QA have no clue what user story they will be testing and blaming dev. This teams are so bad management doesnt understand agile. They stay in different floor and don't talk with scrum team. Till sprint review they ask for product features and dates code drop like waterfall. Our project completely is nonsense as senior people does not understand coding and blame scrum master and team. This place s---s with politics. I wasted two years here plans now to join a proper company as Dell is bad for engineering knowledge.
Somebody has to be on the receiving end of the "blame-thrower". Sure can't be anyone in Product Management (spewing forth nonsensical requirements and last min changes). Can't blame dev - they're just doing what they're told. Management at Dell is ALWAYS blameless so that leaves QA. As Andrew Dice Clay used to say "bend over and let ROVER take over and he'll give you a bone of your own!"
Fairly common IMHO