Tell me more ×  What's a good way to capture user stories when
you have features that are common across multiple UI modes?  For
example, imagine a commercial flight information system,
something someone might use to answer the question "When is
flight UA211 expected to land?"  As is often the case, the
feature of providing schedule information is common underlying
functionality, even though you might ask for it via a desktop
web browser, a mobile browser (where you want to apply different
style to make it more usable), and maybe even via SMS
shortcodes.  Now, that certainly could be a single user story
("As someone meeting a traveller, I want to see flight arrival
information so that I can be at the airport on time"). But that
seems wrong (and would probably be an epic story, anyway).  You
can make it separate user stories ("As a desktop user...", "As a
smartphone user...", etc), which I've done in the past, and the
team just knows to estimate the first one to include all of
functionality, and the subsequent