How do I handle a user story that I complete, but with compromise and need to revisit?
Posted
by
ProfK
on Programmers
See other posts from Programmers
or by ProfK
Published on 2012-06-29T02:44:12Z
Indexed on
2012/06/29
3:22 UTC
Read the original article
Hit count: 469
I have just fulfilled (is that a good term?) two user stories out of a new project backlog I have just built. These are user registration and password reset, both requiring mail. I need to implement a substitute mail component because my initial choice, and a normally reliable one, wasn't working. Because I was focused on delivering the user stories, not debugging the mail component, I swapped it out to deliver working code at sprint end. Do I now log a new support issue for the mailer, or 're-insert' these stories into the backlog? If I do the latter, am I not introducing too much tech detail into user stories?
© Programmers or respective owner