> I personally don't know any software developers that prefer 'stories' of > their user requirements - although I understand the meaning. From my own > experience developers always prefer specific's - they need to know what is > required so they can deliver the requirement.
Software DEVELOPERS need specific requirements to develop an implementation. Software ARCHITECTS need both customer requirements AND stories to design a proper software architecture. Andrey is BOTH of these, and likely could benefit from both requirements as well as stories, depending on his role at the moment. As I stated before here: <http://groups.google.com/group/myLifeOrganized/browse_thread/thread/ 38b936a97cbece22/902d8ecf05ddd818?hl=en&lnk=gst&q=calendar+view +timv#902d8ecf05ddd818> I like the idea of some sort of SIMPLE calendar or schedule "view" of my projects and tasks in MLO; and/or a view of hours assigned to a context (Steve's idea, same thread); but NOT a duplication of a Calendar program (i.e. Outlook), nor adding any additional fields, nor do I need to be able to edit inside a calendar or schedule view -- it need only be a re-arranged visualization of my existing data. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/myLifeOrganized?hl=en -~----------~----~----~----~------~----~------~--~---
