Yesterday while fleshing out user stories, the question came up of whether or not user stories can capture everything, or whether some information should be deferred to specs.
In my opinion, separate specifications are needed because user stories only capture features. It is not a user story that users have unique ids in the database, to name a trivial example. Perhaps I should list a more interesting example: It is not a user story that a single, reusable library handles all alerts for the system. Stories will talk about *specific* alerts, or even possibly about features of alerts in aggregate, but they will never say "alerts are handled by src/Alert.hs which exports the following symbols: ..." If I'm just arguing semantics let me know. It's certainly possible that all *site features* can be captured in user stories alone.
signature.asc
Description: Digital signature
_______________________________________________ Discuss mailing list [email protected] https://lists.snowdrift.coop/mailman/listinfo/discuss
