Condition: user story was planned to be done in the active sprint. While analyzing / working, the circumstances forces not to finish the story (wrong technical concept; business requirements changed; ...). Let's assume, it is not the teams fault, that it came to the situation. What is then best to do, specially in terms of burn down chart and velocity?
a) foresee resolution variant "cancelled" and change to status "done"? If yes, burn down moves closer to the sprint target
b) have beside "done" the status "cancelled" in the workflow. This status also has the meaning of being finished with it (and not that the story would then being forwarded to another sprint), but since there is no benefit for the product, burn down chart is untouched.
What is your experience with this situation?
thanks for feedback, Roland