>> In short I have two questions: >> >> 1) Where is the "Big Picture" kept when working with stories? (see below) >> >> 2) Where do the design go? (
> I think we spend a lot of time talking about what is and isn't > agile. In my opinion, agile is about delivering business value > continuously by being able to respond to changing needs. > As long as what you're doing supports that, I think its OK. > So if you want a "big picture", you might want a concept document or > a specification, etc. that contains that information. > As far as the design, again, agility says that you don't know > everything, so don't design as if you do...expect your designs to > incrementally change and improve. If you want to capture > intermediate designs in a document, then do it, but only if it helps > you. > I'd go so far as to say, do anything you want, as long as you have a > known, measurable return on investment in doing it, and don't stop > delivering business value. That is my gut feeling, too. (see reply to another post on this thread) > --Dave Thanks for chiming in. /Mattias ---------------------------------------------------- http://www.extremeplanner.com Painless software project management for agile teams 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/
