4 ms·
Starting with the UI is a good idea, but completely ignores the functional requirements that aren't embodied in any UI elements - business rules, automated proc
by joshwa 17y ago
Starting with the UI is a good idea, but completely ignores the functional requirements that aren't embodied in any UI elements - business rules, automated processes, workflow, behavior related to integration with other systems, etc.
User stories are great for fleshing out (and flushing out) many of the business requirements, but for applications of any complexity, a more complete requirements gathering and review process is required.
- danielharan 17y agoLast night I spent 1 hour going over an old system's functionality for a dance studio, in preparation for a rewrite. The most surprising thing was the reservation sub-system. "Oh, we don't use that anymore; we've got Google Calendar". That was listed as a "nice to have" in the original docs, but was disposable. With a traditional workflow, we would have spent a days or weeks building something. We can iterate business requirements too - and only build those business rules necessary for the UI we've sketched out.