Tag: user stories

“Requirements engineering” was supposed to ensure that development teams delivered applications that users wanted. That didn’t happen (as the process of requirements engineering itself demonstrated). The answer to giving users what they want turns out to be getting rid of requirements altogether. Requirements exist because everyone recognizes that users aren’t developers. On that understanding, requirements […]

The financial planning site/application Wesabe failed because they didn’t understand how to use scenarios effectively. You can avoid that mistake by realizing that UX scenarios are about life, not about optimizing the human/computer interface. Wesabe was a financial management website/application that didn’t succeed. Instead, it lost out to Mint (which, by the way, was eventually bought […]