4 ms·
The programmers don't have to write the user stories. A UX guy or a product owner can write the stories (which is how you ensure they're relevant). The job of t
by Cakez0r 11y ago
The programmers don't have to write the user stories. A UX guy or a product owner can write the stories (which is how you ensure they're relevant). The job of the programmer is then to create a technical solution that solves a user requirement.
- paulojreis 11y agoI absolutely agree; that's how it should happen. My main contempt is that, in reality, it doesn't. You get "implementation" guys writing user stories, and - in many ways - implementation model thrown into usage model. And, of course, nowhere in this article I found any discussion regarding who should - and which skills are needed to - write user stories. P.S. As I said above, this is a pet peeve of mine. I'm doing a generalization; of course there are developers which are great at writing user stories and understanding users. It's just that I believe in being professional and knowledgeable. If user stories matter, you should get someone with the valid skill set to do it. Not only should you get the skill set on your team, you should get the process! User stories without user data are just plain fiction. It's just the movie your team plays in their heads regarding how the software is used.
- Cakez0r 11y ago> You get "implementation" guys writing user stories That is true... I've seen a fair share of user stories that start "As a developer"...