Innovation teams are often small, multifunctional crews tasked with constant prototyping. Being open, communicative types, they find Agile useful for most projects. Those teams often encounter a common prototyping pain point: Who writes user stories when we don’t have any users? Agile hangs its hat on its ability to respond quickly to user feedback, to create user stories from that feedback, and to release features and content that address what users are demanding at that time. When you are prototyping, however, you don’t usually have users and the traditional user story:
As a (user type/persona), I want to (insert desired action) so I can (insert revolutionary motivation here).
Without users to provide feedback, and without a product for anyone to provide feedback on, how do you address the issue of User Stories? Continue reading