I was thinking today of a client site I was almost deployed to and one of their in-house terms, zero state. Zero state is what you have when you have a list of records and there are zero records. You may want to accommodate for this off-the-happy-path scenario as part of the workflow of a story. A little list of similar concerns are:
- Zero state
- Copy for messages
- "Are you sure?" for deletes
- What if there is an error?
- What if the user doesn't have permissions?
- What if there is a concurrency issue?
- Does the feature need to be wrapped in an on/off switch for ease of empowerment and abandonment in various environments?
- Does the story title make sense?
- Do any new stories come to mind in addressing these questions?
An older concern you don't hear that much about anymore is... what if you double-click a button when submitting a record or refresh the page after submitting a record? Will you make a double entry? I guess this is still worth worrying about.
No comments:
Post a Comment