My actual job was to make sure the tickets were clear, relevant and ready to work on (as opposed to a stream-of-consciousness wishlist from managers). I gathered requirements, represented the devs in planning meetings, cleared their hurdles and QA'd their work. I was basically a prep cook for the devs.
I work with someone who has that job. The stream of consciousness is much preferable. I need to know the big picture, not some distilled set of requirements. Give requirements and I will spend half my time trying to "reverse engineer" the big picture from them, which is a big waste. And an even bigger waste if I get it wrong. Not sure why our industry is so obsessed with obscuring information.
Although I appreciate having someone to move boxes around for me. I cry a little every time I have to go near that horrid UX.
My actual job was to make sure the tickets were clear, relevant and ready to work on (as opposed to a stream-of-consciousness wishlist from managers). I gathered requirements, represented the devs in planning meetings, cleared their hurdles and QA'd their work. I was basically a prep cook for the devs.
I think it was a useful role.