I saw a question pop up that I thought should definitely be discussed with a wider audience
Does anyone have thoughts on if QA should be responsible for writing requirements/user stories?
The original poster felt that there should be “separation of concerns” but that
QA should however examine those stories for scope and testability
I’ve been in two different situations myself
- Development team (test included under that) had no say in requirements/user stories. We were just given them and expected to get the solution together.
- The development team all sat together to talk to requirements. We were given an overarching goal from higher up and it was our job to work together to fully spec this out into user stories as a team.
So I’ve never been solely responsible for writing requirements but I have been involved in the process.
What about you? Have you ever been solely responsible for writing requirements? If not, how have you been involved in the user story writing process?