I am a QA in the IT team of a big global company. Our company expects that requirements/expectations for development and QA work/stories are written by product managers/PM and/or business analysts/BA.
Most PMs/BAs seem to set the requirements well for stories where we have to develop UI, i.e. things you can see on a screen. But, for non-UI things like APIs, they either don't provide requirements or provide superficial requirements. In their stories, they don't even mention basic scenarios which most laypersons could come up with.
For example, say that an API response has a field called
timeOfEvent. Our PM defined it like this
timeOfEvent = Time at which event occurred. This is not helpful for us. Even a layperson would ask us what is the format of
timeOfEvent? Should it be USA date format or something else? Is that just a date or do you also want the exact time down to seconds? There are many examples of how useless our PMs generally are.
As a result, the developers and QA are forced to come up with basic requirements for the stories and lose time. The management acknowledges the problem but does not do anything concrete about it. At best, they request PMs verbally or in an email to set requirements properly. But, the PMs still continue to write stories with sparse details or sometimes even no details, leaving the rest of the team to figure out what exactly needs to be developed and what are the basic/happy path scenarios to be tested.
I feel like telling the PMs to start being useful, instead of just leaving us to do most of their work. But obviously, that is unprofessional and would result in a firing. But, polite requests to PMs have not yielded any results for a long time. So, what should I do to make PMs accountable and give us proper requirements?