Last 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 reservat

Last 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.