"Don't worry about edge cases or errors, this is an MVP" is a very dangerous line of thought that I usually hear from people used to designing for stakeholder demos, rather than production releases.
A demo for a stakeholder, especially a "user proxy", is a very different path from normal use. Any scenario has to contrive a path through every single one of the stakeholder's pet features, so usually it's a checklist approach instead. "We added XYZ like you asked, see?"
In reality, the "as a user I want to use X feature" user story doesn't cut the mustard - and without designing for plausible scenarios, the product ends up being entirely unusable.
If you're not designing for recovery from exceptions, you're not designing a viable product.
If you're not designing for recovery from exceptions, you're not designing a viable product.
There's another type of stakeholder who will refuse to move ahead until the first release covers every use case, which is a great way to never release. A solid scenario helps choose the right end-to-end paths to cover to provide value to some people in a reasonable time frame.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
