Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Ignore dev, qa and management (unless management is boss of your boss). Make your actions transparent to all, and redirect future communication to your boss
"My boss occupied me with this work, I'l do what you're asking as soon as I finish this.
In case management is direct superior to your boss, you need diplomacy, and, again, transparency about your actions
And be prepared to change direction a couple of times -
Wait, why is the dev giving requirements?
Whatever, when there's a bunch of conflicting requirements, highlight them all and provide insight to how they conflict and make everyone involved come to an agreement on how to move forward, this can happen if there's multiple stakeholders with different visions on the path forward.
Now this may or may not be your job to deal with but "someone" should do it before a tangled mess of bullshit is put together that doesn't work.
when your code is a mess but everything work out in the end
When you keep getting +1s on a rant you posted a month ago.
Go big or go home.
SQA here.
What do you even do when dev, other senior QA, your boss and management all give conflicting requirements for a big milestone planning while still ramping up?
My instinct tells me to do what my boss and dev tells me and to come up with the solution that makes the most sense.
No we don't have a product owner ffs. It's like a bizarre waterfall scheme. I have figure out this on my own and hope I made no big mistakes because the ones with the knowledge are unavailable to help. Been thrown in this shit and it's been 3 months I work here. I am honestly trying my best to filter the best out of this.
rant
waterfall
requirements