Skip to main content
Project Management

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • When I wrote my second opinion, I thought exactly about Definition of Done. But I decided to make question more common, that why I don't said about Scrum. Currently we handle security requirements exactly in this way. But I read about "evil stories" and thought, that maybe this approach is more correct. Commented Jun 25, 2015 at 15:06
  • 2
    "Evil stories" seem to be a good way if you have a particular security requirement that applies at the present moment only. If after 1 year you have new "User stories" to which the security issue should apply- that would be difficult to handle IMHO (e.g. somebody forgets to apply the "evil story") Commented Jun 26, 2015 at 7:21