Apologies that I won't every be able to make these discussions, my 8-5 job will
prevent me from doing so.
I think you're on the right track, the user story should be very focused on
that specific story. Unless the user story is for someone forking the snowdrift
website, then libs and databases
On 02/26/2016 01:29 PM, Bryan Richter wrote:
> 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