> Hi, Mattias. Ron's answer is, as usual, excellent, but I thought I'd add a
> couple of questions for you:
Yep, thanks Ron!
>> 1) Where is the "Big Picture" kept when working with stories? (see
>> below)
>>
>> 2) Where do the design go?
> When I read this, I wonder: which big picture? And which design?
Q 1) was with the restriction that the User Story was ripped. I think my option
right now is to not ripping the user story, but to save it if needed. (Maybe
not needed if I still got the Big Picture in my head)
> For any given product, there are lots of different design representations
> one could make, each one of which captures interesting information. And
> before you start building, when you have a complicated branching tree of
> potential paths through the design space, the problem is multiplied.
Agreed, and the design space is spanned with user stories in their simplest
form.
And, therefore I like to keep them.
I like also to think in terms of expanding the User Stories into Use Cases, to
capture the interesting design issues.
> So which parts of the problem that you are looking to represent that
> aren't represented by story cards?
For example: User Interfaces and maybe also non-functional requirements, that
is interfacing to some function, can be expressed in the
"user-story-exapnded-to-a-use-case."
> Thanks,
Does that answer your question?
> William
/Mattias
To Post a message, send it to: [EMAIL PROTECTED]
To Unsubscribe, send a blank message to: [EMAIL PROTECTED]
ad-free courtesy of objectmentor.com
Yahoo! Groups Links
[Non-text portions of this message have been removed]
To Post a message, send it to: [EMAIL PROTECTED]
To Unsubscribe, send a blank message to: [EMAIL PROTECTED]
ad-free courtesy of objectmentor.com
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/extremeprogramming/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
